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.
 >

Similar Messages

Appending a _ in front of the jsp class name when using weblogic.jspc

http://e-docs.bea.com/wls/docs60/jsp/reference.html
 java weblogic.jspc -d /weblogic/classes -keepgenerated primero.jsp
 "rb" <[email protected]> wrote in message
 news:[email protected]...
 >
 > hi,
 >
 > i do
 >
 > java weblogic.jspc -d /weblogic/classes primero.jsp
 >
 > and it only is generated a _primero.class and do not appear
 > the .java ?
 >
 > what i do bad ?
 >
 > thanks for advance
 >
 >
 > Rodrigo Fonseca da Fonseca <[email protected]> wrote:
 > >Hi,
 > >
 > >I'm using weblogic.jspc to compile some jsp fiels. The compilation is
 > >complete and successfully, but the names of generated files .java and
 > >..class are strange.
 >
 >
 >
 > >
 > >For example, compiling a file named change_login_data.jsp, the resulting
 > >files are change95_login_95_data.java and
 > >change95_login_95_data.class. Compiling a file named buy.jsp, the
 > >resulting files are buy.java and buy.class (fine situation). Why???
 > >
 > >I'm using:
 > >
 > >java weblogic.jspc -d c:\jsp_result -classpath
 > >
 >
 >c:\weblogic\myserver\serverclasses;c:\weblogic\lib\weblogicaux.jar;c:\weblo
 gic\classes
 > >-compiler jikes.exe -J-verbose -keepgenerated -verbose
 > >change_login_data.jsp
 > >
 > >
 > >thanks
 > >Rodrigo
 > >
 > >
 > >
 > >Mark Spotswood wrote:
 > >>
 > >> The namespace for java class files is more restrictive
 > >> than for JSP files. We prepend these underscores so
 > >> that if, for example, someone names their JSP "1.jsp",
 > >> we get a class file with a legal name. We did consider
 > >> not doing this for files which started with characters
 > >> we kenw to be valid (in fact we may have put it in a
 > >> service pack), but later found that this was not sufficient
 > >> because its possible to name a jsp file something that
 > >> clashes with java keywords ("class.jsp" for example).
 > >> Rather than making the scheme even more complex,
 > >> we decided to go back to the original sheme of always
 > >> prepending the underscore.
 > >> --
 > >> mark
 > >>
 > >> Mika Moilanen wrote:
 > >>
 > >> > >>>>> "Shankar" == Shankar Roy <[email protected]> writes:
 > >> >
 > >> > Shankar> Problem seems to go away with weblogic510sp4.jar in
 compilation
 > >classpath.
 > >> > Shankar> Shankar.
 > >> >
 > >> > Shankar> Shankar Roy wrote:
 > >> >
 > >> > >> Hi,
 > >> > >> Can anyone tell why when I invoke weblogic.jspc the class file
 that
 > >is
 > >> > >> generated has a _ in front of the class name
 > >> > >>
 > >> > >> java -classpath
 > >> > >>
 >
 >/space/shankar/weblogic/lib/weblogicaux.jar:/space/shankar/weblogic/classes
 /boot:/space/shankar/weblogic/classes:/space/shankar/dev/dev/lib/activation.
 jar:/space/shankar/dev/dev/lib/classes12.zip:/space/shankar/dev/dev/lib/mail
 .jar:/space/shankar/dev/dev/lib/oroinc.jar:/usr/java/lib/classes.zip
 > >> > >> weblogic.jspc -package com.careassured.jsp -commentary login.jsp
 > >> > >>
 > >> > >> produces a class file by the name _login.class
 > >> > >>
 > >> > >> Thanks for any help pointers.
 > >> > >> Shankar.
 > >> >
 > >> > Not with WLS5.1 and weblogic510sp6.jar, we still get '_' prefixed
 > >> > classes...
 > >> >
 > >> > Actually we're suffering quite a lot because of this bug in
 > >> > weblogic.jspc. Are there any plans for fix?
 > >> >
 > >> > --
 > >> > Best Regards,
 > >> > Mika
 > >> > ----------------------------------------------------------
 > >> > [email protected] phone: +358-0-511-23587
 > >> > Nokia Networks, PO box 320, FIN-00045 NOKIA GROUP, Finland
 > >> > ----------------------------------------------------------
 >

Problem using CORBA clients with RMI/EJB servers..!!!???

Hi,
I have a question on using EJB / or RMI servers with CORBA clients using
RMI-IIOP transport, which in theory should work, but in practice has few
glitches.
Basically, I have implemented a very simple server, StockTreader, which
looks up for a symbol and returns a 'Stock' object. In the first example, I
simplified the 'Stock' object to be a mere java.lang.String, so that lookup
would simply return the 'synbol'.
Then I have implemented the above, as an RMI-IIOP server (case 1) and a
CORBA server (case 2) with respective clients, and the pair of
client-servers work fine as long as they are CORBA-to-CORBA and RMI-to-RMI.
But the problem arises when I tried using the RMI server (via IIOP) with the
CORBA client, when the client tries to narrow the object ref obtained from
the naming service into the CORBA idl defined type (StockTrader) it ends up
with a class cast exception.
This is what I did to achieve the above results:
[1] Define an RMI interface StockTrader.java (extending java.rmi.Remote)
with the method,
public String lookup( String symbol) throws RMIException;
[2] Implement the StorckTrader interface (on a PortableRemoteObject derived
class, to make it IIOP compliant), and then the server to register the stock
trader with COS Naming service as follows:
String homeName =....
StockTraderImpl trader =new StockTraderImpl();
System.out.println("binding obj <" homeName ">...");
java.util.Hashtable ht =new java.util.Hashtable();
ht.put("java.naming.factory.initial", args[2]);
ht.put("java.naming.provider.url", args[3]);
Context ctx =new InitialContext(ht);
ctx.rebind(homeName, trader);
[3] Generate the RMI-IIOP skeletons for the Implementation class,
rmic -iiop stock.StockTraderImpl
[4] generate the IDL for the RMI interface,
rmic -idl stock.StockTraderImpl
[5] Generate IDL stubs for the CORBA client,
idlj -v -fclient -emitAll StockTraderImpl.idl
[6] Write the client to use the IDL-defined stock trader,
String serverName =args[0];
String symList =args[1];
StockClient client =new StockClient();
System.out.println("init orb...");
ORB orb =ORB.init(args, null);
System.out.println("resolve init name service...");
org.omg.CORBA.Object objRef
=orb.resolve_initial_references("NameService");
NamingContext naming =NamingContextHelper.narrow(objRef);
... define a naming component etc...
org.omg.CORBA.Object obj =naming.resolve(...);
System.out.println("narrow objRef: " obj.getClass() ": " +obj);
StockTrader trader =StockTraderHelper.narrow(obj);
[7] Compile all the classes using Java 1.2.2
[8] start tnameserv (naming service), then the server to register the RMI
server obj
[9] Run the CORBA client, passing it the COSNaming service ref name (with
which the server obj is registered)
The CORBA client successfully finds the server obj ref in the naming
service, the operation StockTraderHelper.narrow() fails in the segment
below, with a class cast exception:
org.omg.CORBA.Object obj =naming.resolve(...);
StockTrader trader =StockTraderHelper.narrow(obj);
The <obj> returned by naming service turns out to be of the type;
class com.sun.rmi.iiop.CDRInputStream$1
This is of the same type when stock trader object is registered in a CORBA
server (as opposed to an RMI server), but works correctly with no casting
excpetions..
Any ideas / hints very welcome.
thanks in advance,
-hari

On the contrary... all that is being said is that we needed to provide clearer examples/documentation in the 5.1.0 release. There will be no difference between the product as found in the service pack and the product found in the 5.1.1. That is, the only substantive will be that 5.1.1 will also
include the examples.
"<=one way=>" wrote:
With reference to your and other messages, it appears that one should not
expect that WLS RMI-IIOP will work in a complex real-life system, at least
not now. In other words, support for real-life CORBA clients is not an
option in the current release of WLS.
TIA
"Eduardo Ceballos" <[email protected]> wrote in message
news:[email protected]...
We currently publish an IDL example, even though the IDL programmingmodel in Java is completely non-functional, in anticipation of the support
needs for uses who need to use IDL to talk to the Weblogic server,
generically. This example illustrates the simplest connectivity; it does not
address how
to integrate CORBA and EJB, a broad topic, fraught with peril, imo. I'llnote in passing that, to my knowledge, none of the other vendors attempt
this topic either, a point which is telling if all the less happy to hear.
For the record then, what is missing from our distribution wrt RMI-IIOPare a RMI-IIOP example, an EJB-IIOP example, an EJB-C++. In this you are
correct; better examples are forth coming.
Still, I would not call our RMI-IIOP implementation fragile. I would saythat customers have an understandably hard time accepting that the IDL
programming model is busted; busted in the sense that there are no C++
libraries to support the EJB model, and busted in the sense that there is
simply no
support in Java for an IDL interface to an EJB. Weblogic has nothing to doit being busted, although we are trying to help our customers deal with it
in productive ways.
For the moment, what there is is a RMI (over IIOP) programming model, aninherently Java to Java programming model, and true to that, we accept and
dispatch IIOP request into RMI server objects. The way I look at it is this:
it's just a protocol, like HTTP, or JRMP; it's not IDL and it has
practically nothing to do with CORBA.
ST wrote:
Eduardo,
Can you give us more details about the comment below:
I fear that as soon as the call to narrow succeeds, the remainingapplication will fail to work correctly because it is too difficult ot
use an idl client in java to work.It seems to me that Weblogic's RMI-IIOP is a very fragile
implementation. We
don't need a "HelloWorld" example, we need a concrete serious example(fully
tested and seriously documented) that works so that we can get a betteridea
on how to integrate CORBA and EJB.
Thanks,
Said
"Eduardo Ceballos" <[email protected]> wrote in message
news:[email protected]...
Please post request to the news group...
As I said, you must separate the idl related classes (class files and
java
files) from the rmi classes... in the rmic step, you must set a newtarget
(as you did), emit the java files into that directory (it's not clearyou
did this), then remove all the rmi class files from the class path... ifyou
need to compile more classes at that point, copy the java files to theidl
directly is you must, but you can not share the types in any way.
I fear that as soon as the call to narrow succeeds, the remainingapplication will fail to work correctly because it is too difficult otuse
an idl client in java to work.
Harindra Rajapakshe wrote:
Hi Eduardo,
Thanks for the help. That is the way I compiled my CORBA client, by
separating the IDL-generated stubs from the RMI ones, but still I
get a
CORBA.BAD_PARAM upon narrowing the client proxy to the interfacetype.
Here's what I did;
+ Define the RMI interfaces, in this case a StockTrader interface.
+ Implement RMI interface by extendingjavax.rmi.PortableRemoteObject
making
it IIOP compliant
+ Implemnnt an RMI server, and compile using JDK1.2.2
+ use the RMI implementation to generate CORBA idl, using RMI-IIOPplugin
utility rmic;
rmic -idl -noValueMethods -always -d idl stock.StockTraderImpl
+ generate Java mappings to the IDL generated above, using RMI-IIOPplugin
util,
idlj -v -fclient -emitAll -tf src stocks\StockTrader.idl
This creates source for the package stock and also
org.omg.CORBA.*
package, presumably IIOP type marshalling
+ compile all classes generated above using JDK1.2.2
+ Implement client (CORBA) using the classes generated above, NOTthe
RMI
proxies.
+ start RMI server, with stockTrader server obj
+ start tnameserv
+ start CORBA client
Then the client errors when trying to narrow the obj ref from the
naming
service, into the CORBA IDL defined interface using,
org.omg.CORBA.Object obj =naming.resolve(nn);
StockTrader trader =StockTraderHelper.narrow(obj); // THIS
ERRORS..!!!
throwing a CORBA.BAD_PARAM exception.
any ideas..?
Thanks in advance,
-hari
----- Original Message -----
From: Eduardo Ceballos <[email protected]>
Newsgroups: weblogic.developer.interest.rmi-iiop
To: Hari Rajapakshe <[email protected]>
Sent: Wednesday, July 26, 2000 4:38 AM
Subject: Re: problem using CORBA clients with RMI/EJBservers..!!!???
Please see the post on june 26, re Errors compiling... somewherein
there,
I suspect, you are referring to the rmi class file when you are
obliged
to
completely segregate these from the idl class files.
Hari Rajapakshe wrote:
Hi,
I have a question on using EJB / or RMI servers with CORBA
clients
using
RMI-IIOP transport, which in theory should work, but in practice
has
few
glitches.
Basically, I have implemented a very simple server,
StockTreader,
which
looks up for a symbol and returns a 'Stock' object. In the firstexample, I
simplified the 'Stock' object to be a mere java.lang.String, so
that
lookup
would simply return the 'synbol'.
Then I have implemented the above, as an RMI-IIOP server (case
1)
and a
CORBA server (case 2) with respective clients, and the pair of
client-servers work fine as long as they are CORBA-to-CORBA andRMI-to-RMI.
But the problem arises when I tried using the RMI server (via
IIOP)
with
the
CORBA client, when the client tries to narrow the object ref
obtained
from
the naming service into the CORBA idl defined type (StockTrader)
it
ends
up
with a class cast exception.
This is what I did to achieve the above results:
[1] Define an RMI interface StockTrader.java (extending
java.rmi.Remote)
with the method,
public String lookup( String symbol) throws RMIException;
[2] Implement the StorckTrader interface (on a
PortableRemoteObject
derived
class, to make it IIOP compliant), and then the server to
register
the
stock
trader with COS Naming service as follows:
String homeName =....
StockTraderImpl trader =new StockTraderImpl();
System.out.println("binding obj <" homeName ">...");
java.util.Hashtable ht =new java.util.Hashtable();
ht.put("java.naming.factory.initial", args[2]);
ht.put("java.naming.provider.url", args[3]);
Context ctx =new InitialContext(ht);
ctx.rebind(homeName, trader);
[3] Generate the RMI-IIOP skeletons for the Implementation
class,
rmic -iiop stock.StockTraderImpl
[4] generate the IDL for the RMI interface,
rmic -idl stock.StockTraderImpl
[5] Generate IDL stubs for the CORBA client,
idlj -v -fclient -emitAll StockTraderImpl.idl
[6] Write the client to use the IDL-defined stock trader,
String serverName =args[0];
String symList =args[1];
StockClient client =new StockClient();
System.out.println("init orb...");
ORB orb =ORB.init(args, null);
System.out.println("resolve init name service...");
org.omg.CORBA.Object objRef
=orb.resolve_initial_references("NameService");
NamingContext naming=NamingContextHelper.narrow(objRef);
... define a naming component etc...
org.omg.CORBA.Object obj =naming.resolve(...);
System.out.println("narrow objRef: " obj.getClass() ":"
+obj);
StockTrader trader =StockTraderHelper.narrow(obj);
[7] Compile all the classes using Java 1.2.2
[8] start tnameserv (naming service), then the server to
register
the
RMI
server obj
[9] Run the CORBA client, passing it the COSNaming service ref
name
(with
which the server obj is registered)
The CORBA client successfully finds the server obj ref in the
naming
service, the operation StockTraderHelper.narrow() fails in thesegment
below, with a class cast exception:
org.omg.CORBA.Object obj =naming.resolve(...);
StockTrader trader =StockTraderHelper.narrow(obj);
The <obj> returned by naming service turns out to be of the
type;
class com.sun.rmi.iiop.CDRInputStream$1
This is of the same type when stock trader object is registeredin a
CORBA
server (as opposed to an RMI server), but works correctly with
no
casting
excpetions..
Any ideas / hints very welcome.
thanks in advance,
-hari

Using weblogic.jspc

We are trying to use weblogic.jspc for precompiling the jsps in our application. Following the ANT task for doing the same.
 <target name="runJspc" depends="runAssembler">
 <path id="jspc.path.id">
 <path refid="class.path"/>
 <fileset dir="${weblogic.gws.app}/APP-INF">
 <include name="**/*.jar"/>
 </fileset>
 </path>
 <java classname="weblogic.jspc" fork="yes" failonerror="yes">
 <classpath refid="jspc.path.id"/>
 <arg line="-webapp ${weblogic.gws.app}/web -compiler ${javac.exec} -classpath ${gws.cl} -compileAll -d ${weblogic.gws.app}/web/WEB-INF/classes -depend -k -keepgenerated -verbose -verboseJavac"/>
 </java>
 </target>
 For some reason, this target runs forever, without printing any logs or anthing. It simply hangs at "runJspc :".
 To dig into details, I modified the target as follows :
 <target name="runJspc" depends="prepare">
 <path id="jspc.path.id">
 <path refid="class.path"/>
 <fileset dir="${weblogic.gws.app}/APP-INF">
 <include name="**/*.jar"/>
 </fileset>
 <pathelement path="${weblogic.gws.app}/web/WEB-INF"/>
 </path>
 <java classname="weblogic.jspc" fork="yes" failonerror="yes">
 <classpath refid="jspc.path.id"/>
 <arg line="-d ${weblogic.gws.app}/web/WEB-INF/classes -classpath ${gws.cl} -compiler ${javac.exec}" />
 <arg value="-k" />
 <arg value="-compileAll" />
 <arg value="-depend" />
 <arg value="-verboseJavac" />
 <arg value="${weblogic.gws.app}/web/retail/jsp_app/home/ft_home.jsp"/>
 <jvmarg line="-Xms512m"/>
 <jvmarg line="-Xmx512m"/>
 </java>
 </target>
 Now it throws below error & stops.
 runJspc:
 [java] [jspc] warning: expected file /WEB-INF/web.xml not found, tag libraries cannot be resolved.
 [java] <Apr 14, 2005 11:49:19 AM PDT> <Warning> <HTTP> <BEA-101181> <Could not find web.xml under WEB-INF in the doc root: ..>
 Is there any way to resolve one of the above two problems ?

Hi Arun,
 It seems that in the second ant target, you decide to compile just a single jsp, while in the first you were trying to compile the complete jsps in a application.
 But in the second target, you forgot to mention -docroot / -webapp target. As a result, the specific error!!.
 To actually debug the first target, try running the program first on commandline , using weblogic.jspc directly passing the arguments.
 This way , you would have a better control over the target, and may be able to isolate the issue easily.

Problem using SQL Loader with ODI

Hi,
I am having problems using SQL Loader with ODI. I am trying to fill an oracle table with data from a txt file. At first I had used "File to SQL" LKM, but due to the size of the source txt file (700MB), I decided to use "File to Oracle (SQLLDR)" LKM.
The error that appears in myFile.txt.log is: "SQL*Loader-101: Invalid argument for username/password"
I think that the problem could be in the definition of the data server (Physical architecutre in topology), because I have left blank Host, user and password.
Is this the problem? What host and user should I use? With "File to SQL" works fine living this blank, but takes to much time.
Thanks in advance

I tried to use your code, but I couldn´t make it work (I don´t know Jython). I think the problem could be with the use of quotes
Here is what I wrote:
import os
retVal = os.system(r'sqlldr control=E:\Public\TXTODI\PROFITA2/Profita2Final.txt.ctl log=E:\Public\TXTODI\PROFITA2/Profita2Final.txt.log userid=MYUSER/myPassword @ mySID')
if retVal == 1 or retVal > 2:
raise 'SQLLDR failed. Please check the for details '
And the error message is:
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 5, in ?
SQLLDR failed. Please check the for details
 at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
 at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
 at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
 at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
 at com.sunopsis.dwg.cmd.e.i(e.java)
 at com.sunopsis.dwg.cmd.h.y(h.java)
 at com.sunopsis.dwg.cmd.e.run(e.java)
 at java.lang.Thread.run(Unknown Source)

Using WebLogic Server with Oracle9i RAC

A new white paper has been posted to dev2dev -
"Using WebLogic Server with Oracle9i RAC" at
http://dev2dev.bea.com/products/wlserver81/whitepapers/wls_bea_hp.jsp
Abstract:
"This paper presents best practices when using WebLogic Server with Oracle Real Application Clusters. It includes an analysis of
various use-case and failure scenarios and proposes possible recovery solutions. This paper also includes an evaluation of
Transparent Application Failover, a product from Oracle that is functionally similar to WebLogic Server MultiPools."

"satyam" <[email protected]> writes:
Can I use WebLogic Application Server 6.0, the mid level server (not the express
or the enterprise version)
with VisiBroker 4.x ?If you have ejb support - then yes - although you may want to wait for
a future 6.0 rolling patch to get updated IDL generation.
andy

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 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

Precompiling JSPs using weblogic.jspc

Hello,
My question has more to do with getting the Weblogic precompiler to understand <%@ include file="myFilejsp" %> directives.
Test scenario:
In our application, we have used a common JSP page say 'commonJSP' as a header and have included 'commonJSP' in all our other JSP pages.
Suppose my commonJSP is like this:
<%
String hello= "Hello";
%>
and suppose my index.jsp is like this
<%@ include file="commonJSP" %>
<%
System.out.println(hello);
%>
Now when I serve index.jsp to clients it compiles correctly because the commonJSP is included in the source before compiling.
HOWEVER, when precompiling the JSPs in my web application using the <java weblogic.jspc ..> tag in my ant build file, I am getting errors on compiling index.jsp that 'hello' cannot be resolved.
When using the WebLogic JSP compiler, is there any way to tell the compiler to not treat JSP pages as individual 'servlet' classes but look at the 'big picture'?

Anybody ?

Error Using weblogic.jspc --- java.lang.ExceptionInInitializerError

Hi,
 I am trying to use the weblogic.jspc compiler to pre-compile my jsp
 files so that I can verify that they compile w/o having to visit the
 page. I am using Weblogic 4.5.1. I am encountering the following
 error:
 java.lang.ExceptionInInitializerError
 at java.lang.Throwable.<init>(Compiled Code)
 at java.lang.Error.<init>(Compiled Code)
 at java.lang.LinkageError.<init>(Compiled Code)
 at java.lang.ExceptionInInitializerError.<init>(Compiled Code)
 at java.beans.Beans.instantiate(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.processBeanTag(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mXML_THING(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code)
 at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
 at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
 at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
 at weblogic.servlet.jhtmlc.Jhtml2Java$Output.setSourceFile(Compiled
 Code)
 at weblogic.servlet.jhtmlc.Jhtml2Java.outputs(Compiled Code)
 at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
 at weblogic.jhtmlc.runBody(Compiled Code)
 at weblogic.jspc.runBody(Compiled Code)
 at weblogic.utils.compiler.Tool.run(Compiled Code)
 at weblogic.jspc.main(Compiled Code)
 Have any of you seen this? Can you tell me what I am doing wrong
 (Classpath, etc.)?
 Any and all help would be greatly appreciated.
 The command line I am using is:
 java -verbose -classpath
 $CLASSPATH:/apps/weblogic/license:/apps/weblogic/classes:/apps/weblogic/lib/weblogicaux.jar
 weblogic.jspc -d $HOME/weblogic/myserver/classfiles/examples
 100-Welcome.jsp
 Regards,
 Richard


Fixed with a patch CR0737797 and CR062538 for the 6.1 sp3 source line
 Prasanna Yalam

Problem using iPad mirroring with an Apple TV and 4:3 Projector

I'm a teacher and I've been using my iPad 2 in the classroom for about a year and a half. I would use Apple's VGA Adapter to connect to my projector, which worked fine. I just didn't like being tied down, and the dock connector would come loose very easily and lose connection to the projector, which interrupted the flow of the lesson.
So this summer, I got an Apple TV and a projector with an HDMI port so I could start using Airplay Mirroring to get the iPad screen onto the projector. But I'm having trouble with the aspect ratio. Forgive my drawing, but the genius at the Apple store had a hard time understanding my explanation, so I'm hoping this will help show what I mean.
My projector (ViewSonic DLP PJD5133) can be set to either a 4:3 or 16:9 aspect ratio (4:3, 800x600 is the native resolution). My projector screen in the front of the classroom is 4:3, so when the projector is set to 4:3, the image fills up the screen (which is what I want - it needs to be as big as possible so the entire class can see it clearly; plus it means all the output pixels are being used). When the projector is set to 16:9, the image is letterboxed (not ideal unless I'm showing a widescreen video or image).
The Apple TV's native aspect ratio is widescreen, and the iPad's native aspect ratio is 4:3, so if you use Airplay mirroring on a widescreen TV, the Apple TV will pillarbox the image (add horizontal black bars on each side), so that the image will not be stretched/distorted. (I know that it will show widescreen videos and a few widescreen-ready apps without the pillarbox, but the apps I use in class - Keynote, Noteshelf, etc. - don't fall in that category). The effect on my projector screen is a tiny 4:3 image taking up half the area it would have taken if I had used the VGA connection.
So in the Apple TV, I went to Settings>Audio & Video>TV resolution, and chose 800x600 60Hz (the max 4:3 resolution for my projector). Since the Apple TV is natively widescreen, it seems to accomplish this change be stretching the image vertically; but it basically works because the Apple TV home screen fills up the projector screen. However, when I turn on Airplay Mirroring on my iPad, the image does not fill up the screen. The Apple TV still puts a pillarbox on the image, so I end up with a distorted, square image of my iPad screen. It's the right height - the max 600 pixels for my projector - but it's not as wide as it should/could be.
Is there a setting that I'm missing? I understand that the Apple TV has to stretch its home screen image to accommodate the 4:3 resolution, but I think it should be smart enough to realize that if it's receiving a 4:3 image from the iPad and sending it out to a 4:3 TV, it doesn't need to pillarbox the image.
Before you answer - this is not a problem with the projector settings, and my Apple TV is not defective. You could simulate what's happening on your Apple TV, even if it's hooked up to a widescreen TV. In the Apple TV settings, change the TV Resolution to 800x600 as mentioned above (or any other of the 4:3 options). Now go to the Apple TV home screen, and note the amount of space the image is taking up on your screen (on a widescreen TV, it will be pillarboxed, and it will look like it's been squished horizontally). Then turn on Airplay mirroring on the iPad, and you'll see that the iPad image does not have the same width as the Apple TV home screen and it looks square/squished.
Also, while my projector does have a zoom function, it will not magnify the small iPad mirror image correctly (if I were to leave the Apple TV and projector on a 16:9 setting). It cuts off the top and sides. But even if it didn't crop the image, it's a digital zoom, so that option still won't fix the fact that I'm not getting a full 800x600 image on the projector. The same problem would apply if I were to move the projector farther away from the screen (so that the widescreen image takes up the full height of the projector screen, while spilling off the sides). I'll still have a lower resolution image, which isn't ideal since I'm often showing text on the screen through Keynote. Also, widescreen videos wouldn't fit on the screen, and I can't move the projector easily because it's fixed to the ceiling.
Sorry for the long explanation. Any ideas? I'd really appreciate some insight.

We have the same problem, and not only with ipads. Macbook Air is doing something similar. it can only use airplay with 1080 and 720 resolution, so the image is squeezed on a 4:3 projector. We use AppleTV 3 and Mountain Lion OS. We use ATVPRO from Kanex.
Apple must get its act together and fix this, they promise gold and green forests, but nothing works.
DO SOMETHING!

Problem using Time Machine with Seagate BackUp Plus Pls HELP!!

I have a late 2006 iMac (running OS 10.5.8) & am trying to back up using Time Machine with a new Seagate BackUp Plus drive. When I select the Seagate drive in Time Machine it tells me I msut first erase the (Seagate) disk. When I hit ERASE, I get a Time Machine error : COULD NOT UNMOUNT DISK. I see from various posts that 10,5 & 10,6 have issues with some external drives so want to upgrade to Mavericks (to get around this incompatibility issue): HOwever apparently my iMac is too old (by 1 year) to allow this. Can anyone give me any advice on how to get my iMac content backed up via Time Machine using the Seagate BackUP PLus drive I bought (becasue it is supposedly "compatible with PCs & Macs".
Thank you!!
Wendy

Your Seagate drive should work just fine. If it doesn't have any important data on it, try re-formatting it with Disk Utility to blank it out. Or run the Disk verify/repair and see if you can get it to fix any problems.
I have a Drobo FS too. You probably need a firmware update, they issued one a while back to fix problems with Time Machine. Use the Dashboard or download it from their support site, http://www.drobo.com/support/updates.php
Just curious how long you let it run after it "stalled". If it is a big file it could just be taking a while to copy over, do you see activity lights on the USB drive? The first time you use time machine let it run overnight, it's going to take a while, after that it will update quickly.
While you're at it, you might want to verify your start-up disk too with Disk Utility.

How to use weblogic.jspc -J option

Can anyone give me an example on how to use the
 weblogic.jspc -J option? Specifically, I want
 my "-compilerclass" to use a system property
 which will be specified on the command line.
 For example:
 java ... weblogic.jspc ... -compilerclass MyCompilerClass -Dmy.text="hello world"
 or something to that effect.
 Gary F.
 Fast Track Systems, Inc.


-J only seems to work for -X-style arguments to the VM, i.e. you can say
 "-Jms64m".
 -compiler has been broken for a while (see my other post in this group on
 that).
 anders
 "Gary Fong" <[email protected]> wrote in message
 news:[email protected]..
 > Can anyone give me an example on how to use the
 > weblogic.jspc -J option? Specifically, I want
 > my "-compilerclass" to use a system property
 > which will be specified on the command line.
 >
 > For example:
 >
 > java ... weblogic.jspc ... -compilerclass
 MyCompilerClass -Dmy.text="hello world"
 >
 > or something to that effect.
 > --
 > Gary F.
 > Fast Track Systems, Inc.

Java.io.IOException using weblogic.jspc

I've seen a number of similar questions on this but no answers. Can
 anyone provide some insight?
 I have a JSP containing a custom tag library that compiles and executes
 successfully when deployed as a war file under wls 5.1 sp8 but running
 the weblogic.jspc compiler from the command line produces a
 java.io.IOException: cannot resolve '/WEB-INF/tlds/struts-template.tld'
 into a valid tag library.
 The web.xml file includes:
 <taglib>
 <taglib-uri>/WEB-INF/tlds/struts-template.tld</taglib-uri>
 <taglib-location>/WEB-INF/tlds/struts-template.tld</taglib-location>
 </taglib>
 The command I'm using is:
 java -Dweblogic.home=/opt/weblogic
 weblogic.jspc
 -d /home/wmeier/java/StrutsTemplate/build/jsp
 -docroot /home/wmeier/java/StrutsTemplate/web
 -contextPath StrutsTemplate
 -encoding default
 -keepgenerated
 -g
 introduction.jsp
 I can get the jsp compiler to work when I change the taglib uri
 declaration from
 <%@ taglib uri='/WEB-INF/tlds/struts-template.tld'...
 to
 <%@ taglib uri='/tlds/struts-template.tld'
 This modified uri also works as a war file under WebLogic but fails
 under the Tomcat 3.2 reference implementation.
 Does anyone have any ideas how I can get the compiler to work without
 hacking the taglib uri?
 Thanks,
 Bill Meier


CeciNEstPasUnProgrammeur wrote:
Hm, well... the API docs say for non-existing files you get an IllegalArgumentException, and IOException is for "no application registered" or "application won't start"...
Just a guess: is the firewall blocking the execution?I don't think it is a fire wall issue since everything runs on the same machine (the file is created and invoked on the same machine)
Any other ideas?

Any problem using PC fonts with Fontbook?

Hi all.
Are there any potential issues using PC fonts with Fontbook? I've downloaded a free internet font, ran the "Validate File" option, then loaded the font into Fontbook. Afterwards, I also ran "Validate Font" and it checked out okay.
It seems to be working, but I'm wondering if there is cause for concern that maybe down the line something funny will happen?
Any insight into this?
B.

It seems to be working, but I'm wondering if there is cause for concern that maybe down the line something funny will happen?
No, a font is just a font. All PC .ttf and .ttc fonts work in OS X. Windows Type 1 PostScript fonts (the ones with matching .pfb and .pfm extensions) do not.
The only real problem with free fonts is that the majority of them are not made well and can cause various problems because of it. Read section 14 of Font Management in OS X to see what those issues can be.
The link, or one of the links above directs you to my personal web site. While the information is free, it does ask for a contribution. As such, I am required by Apple's rules for these discussions to include the following disclaimer.
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Problem using weblogic.jspc with wls6.1

Similar Messages

Maybe you are looking for