Problem in using Weblogic 5.1

hello friends,
I have a Problem in Using Weblogic 5.1
I am using weblogic 5.1 Enterprise on Linux 2.2.16 SuSE (7.0) with
Dual Celeron 550MHz and 1GB RAM. The server runs our web application
which uses the servelt, JSP and XSQL technology. The problem is
that often i receive ASSERTION FAILURES where after the jsp's stop
displaying content. Is this a Weblogic administration problem or
the underlying OS problem. Kindly advice.
Thankx in Advance
Yajneesh sabharwal

Is this an issue with the "T-engine" or the "J-engine"? Are you using a
ubbconfig file or weblogic.properties file? Can you post the stack trace?
This may be an known issue and simply require you to install the latest
service pack for WLS 5.1 (aka. J-engine)...
Mary Ann Slavin wrote:
Accordning to the Software Product Information (SPI) for WLE 5.1 it is
available on the following Linux versions so this could be a problem
with the version you are running.
"BEA WebLogic Enterprise 5.1 software for Red Hat Linux 6.2 and Reliant
Unix 5.45 is available separately. "
MAS
yajneesh Sabharwal wrote:
hello friends,
I have a Problem in Using Weblogic 5.1
I am using weblogic 5.1 Enterprise on Linux 2.2.16 SuSE (7.0) with
Dual Celeron 550MHz and 1GB RAM. The server runs our web application
which uses the servelt, JSP and XSQL technology. The problem is
that often i receive ASSERTION FAILURES where after the jsp's stop
displaying content. Is this a Weblogic administration problem or
the underlying OS problem. Kindly advice.
Thankx in Advance
Yajneesh sabharwal

Similar Messages

Problem when using weblogic.jspc from an IDE

I am trying to call JSPC from an IDE (as part of an Eclipse Builder). To optimize performance I want to avoid to spwan a new process. So I am trying to call weblogic.jspc's main method directly from the IDE. Everything works fine for simple simple pages.
 But when the page refers to a tag library with a tag providing a TagExtraInfo class, weblogic.jspc complains about the class not extending the TagExtraInfo base class although it does:
 Errors encountered while compiling 'D:\vrp-localdeploy\applications\wot\WOT' :
 Translation of /rentalcar/tiles/i18n/CarCapacityView.jsp failed: (line 17): Error in using tag library uri='/tags/i18n' prefix='i18n': For tag 'bundle', extra info class 'org.apache.taglibs.i18n.BundleTEI' does not extend javax.servlet.jsp.tagext.TagExtraInfo
 I could not figure out what exactly causes the problem. Using exactly the same settings workes just fine.
 Any suggestions?

The full stack trace reads as follows:
 
 Errors encountered while compiling 'D:\vrp-localdeploy\applications\wot\WOT' :
 
 Translation of /common/include/i18n/definitions.inc failed: (line 17): Error in using tag library uri='/tags/i18n' prefix='i18n': For tag 'bundle', extra info class 'org.apache.taglibs.i18n.BundleTEI' does not extend javax.servlet.jsp.tagext.TagExtraInfo
 
 at weblogic.jspc.runJspc(jspc.java:559)
 at weblogic.jspc.runBodyInternal(jspc.java:410)
 at weblogic.jspc.runBody(jspc.java:319)
 at weblogic.utils.compiler.Tool.run(Tool.java:146)
 at weblogic.utils.compiler.Tool.run(Tool.java:103)
 at weblogic.jspc.main(jspc.java:708)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.compileJSP(PresentationBuilder.java:1173)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.checkResource(PresentationBuilder.java:718)
 at tui.vrp.tools.presentation.builder.PresentationBuilder$PresentationDeltaVisitor.visit(PresentationBuilder.java:102)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
 at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.incrementalBuild(PresentationBuilder.java:1268)
 at tui.vrp.tools.presentation.builder.PresentationBuilder.build(PresentationBuilder.java:677)
 at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:593)
 at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
 at org.eclipse.core.runtime.Platform.run(Platform.java:783)
 at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
 at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
 at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:231)
 at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
 at org.eclipse.core.runtime.Platform.run(Platform.java:783)
 at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:234)
 at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:253)
 at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:282)
 at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139)
 at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:200)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
 
 Unfortunately it doesn't really give any real reason - it is a general piece of code in jspc to report problems.
 
 But I dug a lot bit deeper into the code and realized that the original problem is a ClassCastException in line 1290 of class StandardTagLib, which reads as follows:
 
 tagextrainfo = (TagExtraInfo)Beans.instantiate(classloader, s3);
 
 This looks quite obvious that the class named by s3 simply is no extension of TagExtraInfo, but unfortunately the only class with that name being referenced by the class path does extend this class. I wondered what the problem might be and came up with the following answer:
 
 The class of the bean instantiated by Beans.instantiate extends a class with the name "javax.servlet.jsp.tagext.TagExtraInfo" which is cast to another class with exactly the same name, but a different class loader. Since neither of the class loaders is parent of the other one, both classes are not considered being the same class although they have the same name. Sounds weird, but exactly this is the problem!
 
 Where does it come from and why it works fine when the tool is executed in a separate thread or on the console?
 
 From my understanding the problem is caused in line 395 of the class weblogic.jspc:
 
 GenericClassLoader genericclassloader = new GenericClassLoader(classpathclassfinder);
 
 This line of code creates a class loader not knowing a parent class loader by which the class weblogic.jspc was loaded. All classes weblogic.jspc is using or calling will be loader by either the same or a parent class loader - this is important to understand. Since TagExtraInfo is directly referenced by StandardTagLib one instance of the class object (the object of type class) will be generated and linked when the class StandardTagLib is instantiated for the first time by the class loader which loaded weblogic.jspc (or by its parent). This is consequence which can not be avoided.
 
 But now look at line 1290 of class StandardTagLib: It explicitly requests the class to be loaded by the GenericClassLoader instantiated in line 395 of the class weblogic.jspc. This class loader, off course, is not aware of the same class just being loaded by another class loader since it has no knowledge of it. It simply creates a fresh copy of the class object, which only differs in the reference to the class loader which created this class object.
 
 Actually, I figured that the following line of code replacing the upper one, would resolve the problem:
 
 GenericClassLoader genericclassloader = new GenericClassLoader(classpathclassfinder, this.getClass().getClassLoader());
 
 Doing this, the GenericClassLoader would know its logical parent by reference and would implicitly - thanks to the implementation of java.lang.ClassLoader - try to find the class using its parent first, would find a valid class, and hence use the same instance of the class object instantiated by the parent class loader. The problem would be solved.
 
 It works fine in the console or under a running application server, because they will always have the weblogic jar in their system class path. ClassLoaders not having a parent are implied to have the system class loader as their parent - the piece of code does work in this case.
 
 Under Eclipse this is no option, off course. We would restrain us to exactly this version of the APIs used by the weblogic version in the system class path.
 
 I was trying to patch this myself by extending weblogic.jspc by my own class to pass on a proper class loader knowing its parent, and I was sort of successful: The problem disappeared. But I can't gain exactly what I am looking for, because the method runJspc with four parameters (around line 447) of weblogic.jspc is private to the class and its public brother always passes true to this method as the fourth parameter - causing jspc to recompile all JSPs instead of just the requested ones.
 
 Everything refers to WL81SP3.
 
 That's were I got stuck currently. I have read some postings about this problem in the internet - some dating far back into the history. So, I have the impression that there have been some folks around with the same problem. I think the patch I suggested does not any harm and I could simply use jspc in my builder without any problems.
 
 Regards,
 
 Elmar Schwarz

Problem in using Weblogic 6.1 with Oracle 9i

Hi,
Has anybody experiensing problems in creating connection from Weblogic6.1 to Oracle
9i using thin driver?
We have a piece of codes that works fine with Weblogic 6.1 and Oracle 8.1.7 but
failed to create database connection when we upgrade to database to 9i (the same
code works fine without weblogic).
Thanks
Li
[email protected]

It works after I put the new oracle driver ahead of the weblogic stuff.
Thanks
Li
Joseph Weinstein <[email protected]> wrote:
You should make sure you have the same Oracle driver in the server
classpath, as works in the standalone case. Note that we ship a
thin driver too, so your newer one will ahve to be ahead of all
the weblogic stuff in the server classpath.
Joe
Li Wang wrote:
After upgraded our oracle server to 9i, we found that our applicationdoes not
work. So, I wrote a simple test program that just creates a connectionand exec
a query. The program works find with 9i by itself (of cause). But,when I put
it in Weblogic 6.1 (as Startup class), there are problems.
First, it takes 833700ms to create a connection (It takes 981ms tocreate a connection
outside wls, it takes 900ms to create a connection to oracle8.1.7 insidewls).
Then, it gets "java.sql.SQLException: ORA-00600: internal error code,arguments:
[ttcgcshnd-1], [0], [], [], [], [], [], []"
while executing the query.
We run weblogic and oracle on Windows2000.
The code looks like:
Class.forName("oracle.jdbc.driver.OracleDriver");
String username = "yourusername";
String password = "yourpassword";
String host = "yourhost";
String sid = "yoursid";
String dbURL = "jdbc:oracle:thin:@" + host +":1521:" + sid;
String sql = "select * from yourtable";
System.out.println(dbURL);
Connection connection = DriverManager.getConnection (dbURL, username,password);
Statement statement = connection.createStatement();
statement.executeQuery(sql);
statement.close();
connection.close();
"Jignesh Patel" <[email protected]> wrote:
1. Are you able to create connection pool using Oracle 9i THIN driver
? i.e Define
connection pool & make initial connection => 1. At the time of startup
weblogic
will create connections defined in connection pool.
2. Can you post your error message ?
Thanks
Jignesh Patel
"Li Wang" <[email protected]> wrote:
Hi,
Has anybody experiensing problems in creating connection from Weblogic6.1
to Oracle
9i using thin driver?
We have a piece of codes that works fine with Weblogic 6.1 and Oracle
8.1.7 but
failed to create database connection when we upgrade to database
to
9i
(the same
code works fine without weblogic).
Thanks
Li
[email protected]

My problem in using weblogic Datasource and proxy user

Hello
I create a DataSource in Weblogic that connect to the database by a proxy user and I have a client application that use this DataSource and create a proxy session , I've written my client application (it's a stand alone client application) code below :
public static void main(String [] args) {
OracleConnection conn=null;
javax.sql.DataSource ds=null;
Hashtable env = new Hashtable();
env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
env.put(Context.PROVIDER_URL, "t3://127.0.0.1:7001");
try{
Context context=new InitialContext( env );
ds=(javax.sql.DataSource) context.lookup ("OracleConnection2");
conn=(OracleConnection) ds.getConnection();
java.util.Properties prop = new java.util.Properties();
prop.put(OracleConnection.PROXY_USER_NAME, "web_user1");
prop.put(OracleConnection.PROXY_USER_PASSWORD,"web_user1");
conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, prop);
if (conn.isClosed()){
System.out.println("Connection closed");
return;
testJDBC(conn,true);
for(int k=0;k<10;k++){
testJDBC(conn,false);
conn.close(OracleConnection.PROXY_SESSION);
conn.close();
}catch(Exception ex){
ex.printStackTrace();
It works but my problem is that in line "prop.put(OracleConnection.PROXY_USER_PASSWORD,"web_user1")" or line "prop.put(OracleConnection.PROXY_USER_NAME, "web_user1");"
Let me to mention a scenario :
*1- I type a wrong username or password in my client application and I run the client application it shows me this error : invalid username/password*
*this error is acceptable*
*2- then I correct the wrong username or password immediately and run the application again , it shows me this error (at line conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, prop)) :*
java.sql.SQLException: Closed Connection
 at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
 at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
 at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
 at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
 at oracle.HRFacadeClient.main(HRFacadeClient.java:38)
*3- I run the application again (by correct username and password) but this time it shows me this error :*
java.sql.SQLException: Unsupported feature
 at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
 at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
 at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
 at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
 at oracle.HRFacadeClient.main(HRFacadeClient.java:38)
*4 - if I repeat running the application for multi times every time it shows me the previous error*
*5- I wait about one minute the problem solved and my application can create proxy session *
the result is that if I wanna create proxy session by wrong username or password and I get "Invalid username/password" error message , then after correcting username or password I have to wait about one minute and then run the application again_
Do you know how I can overcome this problem ?
Thank you

Hi Jamshid,
There is same problem observed few days back with us, and we have used the below code, and it got solved. Actually there is a problem observed while using proxy connections on weblogic.
if(conn instanceof weblogic.jdbc.extensions.WLConnection){
 weblogic.jdbc.extensions.WLConnection cn=(weblogic.jdbc.extensions.WLConnection)conn;
 cn.clearStatementCache();
http://rocksolutions.wordpress.com/2010/06/04/connection-pool-issue-on-weblogic/
Hope this helps.
Thanks

Problem While using Applet Reqd classes using Weblogic 5.1

Hi All,
Here is my problem while using other classes from the Applet gives an error:NoClassDefFound,
I have also put the applet reqd. classes in a jar file and placed this jar along with the applet
in weblogic/myserver/serverclases,
my tag in the html file is as follows:
<applet code="MyApplet.class" archive="voucher.jar"
codebase="/classes/" >
</applet>
is there any problem with my tag or directory structure,
It would be great ful and thanks for helping in solving this problem.
sai.

Is this an issue with the "T-engine" or the "J-engine"? Are you using a
ubbconfig file or weblogic.properties file? Can you post the stack trace?
This may be an known issue and simply require you to install the latest
service pack for WLS 5.1 (aka. J-engine)...
Mary Ann Slavin wrote:
Accordning to the Software Product Information (SPI) for WLE 5.1 it is
available on the following Linux versions so this could be a problem
with the version you are running.
"BEA WebLogic Enterprise 5.1 software for Red Hat Linux 6.2 and Reliant
Unix 5.45 is available separately. "
MAS
yajneesh Sabharwal wrote:
hello friends,
I have a Problem in Using Weblogic 5.1
I am using weblogic 5.1 Enterprise on Linux 2.2.16 SuSE (7.0) with
Dual Celeron 550MHz and 1GB RAM. The server runs our web application
which uses the servelt, JSP and XSQL technology. The problem is
that often i receive ASSERTION FAILURES where after the jsp's stop
displaying content. Is this a Weblogic administration problem or
the underlying OS problem. Kindly advice.
Thankx in Advance
Yajneesh sabharwal

Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio

We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
 throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
 at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
 at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
 at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
 at weblogic.kernel.Kernel.initialize(Kernel.java:138)
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
 throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more

uday naik <> writes:
The thin-client isn't supported on 6.1, I'm not sure what you are doing.
andy
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
 throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
 at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
 at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
 at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
 at weblogic.kernel.Kernel.initialize(Kernel.java:138)
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
 throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more

Problem in Using Log4J with Weblogic 9.2

I am using Weblogic 9.2 and Log4j.
By using Admin console I set the Severity Level to WARNING and inside my java code is given below:
Logger logger = Log4jLoggingHelper.getLog4jServerLogger();
if (logger.isEnabledFor(Priority.DEBUG)){
logger.debug("DEBUG - Test Debug message");
logger.info("DEBUG - Test Info Message");
logger.warn("DEBUG - Test Warning Message");
logger.error("DEBUG - Test Error Message");
logger.fatal("DEBUG - Test Fatal Message");
Somehow the logger.isEnabledFor(Priority.DEBUG) returning 'TRUE' and the follwoing message is displayed.
<Nov 29, 2006 2:44:04 PM EST> <Warning> org.apache.log4j.Category> <000000> <DEBUG - Test Warning Message>
<Nov 29, 2006 2:44:04 PM EST> <Error> <org.apache.log4j.Category> <000000> <DEBUG - Test Error Message>
<Nov 29, 2006 2:44:04 PM EST> <Info> <org.apache.log4j.Category> <000000> <DEBUG - Test Fatal Message>
NOTE - The logger.debug() and logger.info() methods are not invoked because of the severity level to 'WARNING' in the console.
I would like to know why the Somehow the logger.isEnabledFor(Priority.DEBUG) is having a value of 'TRUE'.
I expected only the Somehow the logger.isEnabledFor(Priority.ERROR) will have the value of 'TRUE'.

Did you get an answer to your question? I have the same problem with WebLogic 10.0.

Problem using weblogic.jspc with wls6.1

 I've got this error using weblogic.jspc on jsp that works fine with the compiler
 of 5.1, is this a bug?
 java.lang.NullPointerException
 at weblogic.management.Admin.getServer(Admin.java:1252)
 at weblogic.servlet.internal.dd.ServletEntityResolver.initServerMBean(ServletEntityResolver.java:69)
 at weblogic.servlet.internal.dd.ServletEntityResolver.resolveEntity(ServletEntityResolver.java:94)
 at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:749)
 at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:566)
 at weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1139)
 at weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2215)
 at weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(Compiled
 Code)
 at weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(Compiled
 Code)
 at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
 Code)
 at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
 at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:175)
 at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:311)
 at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:327)
 at weblogic.servlet.internal.dd.DescriptorLoader.initialize(DescriptorLoader.java:242)
 at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:176)
 at weblogic.servlet.internal.dd.DescriptorLoader.loadDescriptor(DescriptorLoader.java:396)
 at weblogic.jspc.runBodyInternal(Compiled Code)
 at weblogic.jspc.runBody(jspc.java:169)
 at weblogic.utils.compiler.Tool.run(Tool.java:79)
 at weblogic.jspc.main(Compiled Code)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
 [java.lang.NullPointerException]
 at java.lang.Throwable.fillInStackTrace(Native Method)
 at java.lang.Throwable.fillInStackTrace(Compiled Code)
 at java.lang.Throwable.<init>(Compiled Code)
 at java.lang.Error.<init>(Error.java:50)
 at weblogic.utils.NestedError.<init>(NestedError.java:24)


Please post your full description. I can't see what you're replying to (must
 be too old).
 Alex
 "Gregory Chazalon" <[email protected]> wrote in message
 news:3c7383a8$[email protected]..
 > I've got te same problem (NullPointerException at the same line code in
 the same class). The most disturbing is that the weblogic.jspc works fine
 with wl6.1 SP2 but fails with wl6.1 SP1.
 >
 > Do you have a solution ? Can I download a CRXXXX.jar that fixes it ?
 >
 > I will appreciate any help.
 >

Problem modifying the connection details in a Report when using Weblogic 12

Hi
I have a j2ee application that uses the Java Reporting Component (JRC). At runtime, the code programmatically changes the connection type and schema name of a crystal report before running it. The connection that was used when designing the report is replaced with new JNDI parameters pointing to a Weblogic/Oracle datasource.
The application works perfectly when using Weblogic 11, but the same code and report fails when deployed to Weblogic 12.
I used Version 12.2.207.916 of the JRC, and updating to the most current version I could find (12.2.217) did not solve the problem.
The code snippet below shows how the connection and schema name is replaced for each of the tables in the report (not all the code is shown here)...
        PropertyBag propertyBag = new PropertyBag();
        propertyBag.put("Database DLL", "crdb_jdbc.dll");
        propertyBag.put("JNDI Datasource Name", jndiName);
        propertyBag.put("Initial Context", "");
            while (tableList.hasNext()) {
                ITable table = tableList.next();
                ITable tableNew = (ITable) table.clone(true);
                IConnectionInfo connectionInfo = table.getConnectionInfo();
                connectionInfo.setAttributes(propertyBag);
                connectionInfo.setKind(ConnectionInfoKind.SQL);
                tableNew.setQualifiedName(newQualifier + "." + table.getName());
                tableNew.setConnectionInfo(connectionInfo);
                dbController.setTableLocation(table, tableNew);
The setTableLocation() function throws the following exception ...
2014-05-13 16:46:27,173 ERROR [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] JRCCommunicationAdapter         detected an exception: Unexpected database connector error
                at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2409)
                at com.crystaldecisions.reports.dataengine.datafoundation.AddDatabaseTableCommand.new(SourceFile:529)
                at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
                at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
                at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)
                at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.byte(SourceFile:1079)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1167)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:167)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:529)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:527)
                at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:525)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:424)
                at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:352)
                at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)
                at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)
                at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)
                at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)
                at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)
                at com.crystaldecisions.sdk.occa.report.application.ds.a(SourceFile:186)
                at com.crystaldecisions.sdk.occa.report.application.an.a(SourceFile:108)
                at com.crystaldecisions.sdk.occa.report.application.b0.if(SourceFile:148)
                at com.crystaldecisions.sdk.occa.report.application.b0.b(SourceFile:95)
                at com.crystaldecisions.sdk.occa.report.application.bb.int(SourceFile:96)
                at com.crystaldecisions.proxy.remoteagent.UndoUnitBase.performDo(SourceFile:151)
                at com.crystaldecisions.proxy.remoteagent.UndoUnitBase.a(SourceFile:106)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:2159)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:543)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:3898)
                at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(SourceFile:2906)
                at com.systest.reporting.engine.crystal.CrystalReportEngine.replaceConnection(CrystalReportEngine.java:523)
                at com.systest.reporting.engine.crystal.CrystalReportEngine.changeDataSource(CrystalReportEngine.java:449)
                at com.systest.CrystalReportPane.setReportDataSourceDetails(CrystalReportPane.java:170)
                at com.systest.CrystalReportPane.commandLoad(CrystalReportPane.java:136)
                at com.systest.ReportRunner.CrystalReport.Load(CrystalReport.java:401)
                at com.systest.ReportRunner.SaveReportToFile(ReportRunner.java:1385)
Any idea what I can do to fix this ?
Thanks in advance!

Last reference in any documentation re. version of supported weblogic is 10.3.x. And it may very well be that things worked in weblogic 11, but as versions go by the differences get bigger and eventually the app stops working.
I'll ping the Program Manager for definitive info and future support. Once I have the info, I'll update this Discussion.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Problem in retriving varray when using weblogic connection pool

Hi,
I had similar problem when we I am using the weblogic connection pool. I had similar setup i.e weblogic 5.1 servicepack9 and oracle 8.1.7.
I cofigarud the weblogic connection pool using Oracle thin driver.
But if I am using with oracle thin driver directly I am able to retrive.
If any one know how to retrive varray from procedure using weblogic connection pool please send me it.
Thanx.
Bye,
Satya

http://docs.oracle.com/javase/6/docs/api/java/sql/Connection.html#setAutoCommit(boolean)

Error While reading CLOB from Oracle using WebLogic Connection Pool, Works fine with out using pool

PROBLEM DESCRIPTION :
     When I try to read a clob from Oracle, I receive "ORA-03120: two-task
conversion routine: integer overflow" Error.
     This error occurs only for CLOB Type and only if I try to connect to
Oracle using WebLogic JDriver/Oracle POOL.
     IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
connection to ORacle with out any problem.
     Below Please find the JAVA CODE for Both Working and NON Working .
Created a Connection Pool as:
Name: MyJDBCConnectionPool
URL : jdbc:weblogic:oracle
DIRVER:weblogic.jdbc.oci.Driver
NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
Driver myDriver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection mconn =
myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection mconn =
myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
ERROR MESSAGE:
     ORA-03120: two-task conversion routine: integer overflow
I appreciate your help on this problem.

PROBLEM DESCRIPTION :
     When I try to read a clob from Oracle, I receive "ORA-03120: two-task
conversion routine: integer overflow" Error.
     This error occurs only for CLOB Type and only if I try to connect to
Oracle using WebLogic JDriver/Oracle POOL.
     IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
connection to ORacle with out any problem.
     Below Please find the JAVA CODE for Both Working and NON Working .
Created a Connection Pool as:
Name: MyJDBCConnectionPool
URL : jdbc:weblogic:oracle
DIRVER:weblogic.jdbc.oci.Driver
NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
Driver myDriver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection mconn =
myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection mconn =
myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
ERROR MESSAGE:
     ORA-03120: two-task conversion routine: integer overflow
I appreciate your help on this problem.

Web services with Jdeveloper using weblogic as server

Hi,
I try to test creating PL/SQL web services by using a connection hosted by weblogic server instead of OC4J. The problem is what I try to publish a package of the database in the second stage when it asks for the connection to use, in the list I don't found the connection I create to weblogic . It presents as choice only connections used the server OC4J.
I do not Know if it is possible to publish a package as web service by using weblogic server connection, and how to do it.
can anyone help me please .
Nawal

Web services can only be published to BEA if you install Apache SOAP on BEA and use the Apache SOAP option of JDeveloper. The J2EE Web Services implementation framework is specific to Oracle9iAS.
The PL/SQL Web Services server implementation is based on the J2EE Web Services option and as a result is not really portable to BEA.
To publish a PL/SQL Web service on BEA with JDeveloper you would have to write the Java wrapper code to invoke the stored procedure using standard JDBC and then publish that Java class as a Web service using Apache SOAP. Then if you had Apache SOAP installed on BEA you would be set.
Portability of Web services implementations is a big feature coming with JAX-RPC - currently what most vendors have is interoperability between implementations because of things like SOAPBuilders and WS-I. When JAX-RPC becomes part of J2EE 1.4 roughly in June and vendors start putting out implementations on it you should get closer to portability.
In the meantime, the easiest way to get portability is to use the same SOAP server on both servers - Apache SOAP is a good example.
Hope this helps.
Mike

Problem in starting weblogic server as proxy

I am using weblogic server as Proxy to forward the requests to weblogic cluster.
When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
I am Pasting my complete logs below.
Setting JVM memory params for server IRISProxy
Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
WLS Production Mode=true
./startWebLogic.sh[68]: B: not found.
maxfiles=8192
CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
* 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.1.05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
Starting WLS with line:
/home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
Bad level value for property: com.iplanet.services.debug.level
Bad level value for property: com.sun.identity.agents.logging.level
Bad level value for property: com.sun.am.policy.amFilter.audit.level
<Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
<Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
<Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
 at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
 at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
 at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
Can someone help me in solving this problem
Thanks
Kris

I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
WebLogic Temporary Patch for CR211812
WebLogic Temporary Patch for CR235145
Once i commented the above patches in the CLASSPATH.
The issue is resolved.

Problem in using web logic server

I have following problems in using the weblogic server 8.1.2
1. Under which folder jsp & html files should be stored?
2. When I run the weblogic server using web logic work shop,
I get the following error message.
"Low virtual memory".
My pc is running on Windows 2000 Professional.
Please give me solution for both of my problems.
My thanks in advance.

1) somedirectory/yourwebapp/
2) get more memory , 1Gig is a good start

Problem when using a new class "File" in JSP

I'm using Weblogic 4.52sp2 under Solaris 2.6 with JDK 1.2.1_04. I've got a problem with a JSP that uses a commercial bean which contains a specific "File" class. This class has its own package: com.jspsmart.upload.File. While compiling, Weblogic raises an exception:
 Fri Mar 09 14:41:38 CET 2001: <ServletContext-Servlets> weblogic.servlet.JSPServlet: Generated java file: /data/html/compiledJSP/_jspsmartupload/_jsp/_sample2.java
 Fri Mar 09 14:41:43 CET 2001:<E> <ServletContext-Servlets> weblogic.servlet.JSPServlet: Compilation of /data/html/compiledJSP/_jspsmartupload/_jsp/_sample2.java failed:
 /data/html/compiledJSP/_jspsmartupload/_jsp/_sample2.java:46: Ambiguous class: java.io.File and com.jspsmart.upload.File
 f = new File("/data/html/jspsmartupload/jsp/sample2.jsp");
 I looked at the .java generated file but it seems that everything is OK: f is a java.io.File
 public class _sample1 extends weblogic.servlet.jsp.JspBase implements weblogic.servlet.jsp.StaleIndicator {
 // StaleIndicator interface
 public boolean _isStale() {
 java.io.File f = null; long lastModWhenBuilt = 0L, lastMod = 0L;
 f = new File("/data/html/jspsmartupload/jsp/sample1.jsp");
 lastModWhenBuilt = 984144952000L;
 lastMod = f.lastModified();
 if (!f.exists() || lastMod > lastModWhenBuilt) return true;
 return false;
 We can't neither change the bean (no sources) nor Weblogic JSP engine (of course). Has anyone a solution ?
 [att1.html]


i think you should try this
 f = new java.io.File("/data/html/jspsmartupload/jsp/sample1.jsp");
 "Laurent PAILLARD" <[email protected]> wrote in message
 news:[email protected]...
 I'm using Weblogic 4.52sp2 under Solaris 2.6 with JDK 1.2.1_04. I've got a
 problem with a JSP that uses a commercial bean which contains a specific
 "File" class. This class has its own package: com.jspsmart.upload.File.
 While compiling, Weblogic raises an exception:
 Fri Mar 09 14:41:38 CET 2001: <ServletContext-Servlets>
 weblogic.servlet.JSPServlet: Generated java file:
 /data/html/compiledJSP/_jspsmartupload/_jsp/_sample2.java
 Fri Mar 09 14:41:43 CET 2001:<E> <ServletContext-Servlets>
 weblogic.servlet.JSPServlet: Compilation of
 /data/html/compiledJSP/_jspsmartupload/_jsp/_sample2.java failed:
 /data/html/compiledJSP/_jspsmartupload/_jsp/_sample2.java:46: Ambiguous
 class: java.io.File and com.jspsmart.upload.File
 f = new File("/data/html/jspsmartupload/jsp/sample2.jsp");
 I looked at the .java generated file but it seems that everything is OK: f
 is a java.io.File
 public class _sample1 extends weblogic.servlet.jsp.JspBase implements
 weblogic.servlet.jsp.StaleIndicator {
 // StaleIndicator interface
 public boolean _isStale() {
 java.io.File f = null; long lastModWhenBuilt = 0L, lastMod = 0L;
 f = new File("/data/html/jspsmartupload/jsp/sample1.jsp");
 lastModWhenBuilt = 984144952000L;
 lastMod = f.lastModified();
 if (!f.exists() || lastMod > lastModWhenBuilt) return true;
 return false;
 We can't neither change the bean (no sources) nor Weblogic JSP engine (of
 course). Has anyone a solution ?

Problem in using Weblogic 5.1

Similar Messages

Maybe you are looking for