ExceptionInInitializer when running weblogic.jspc

I am getting the following error when running weblogic.jspc:
 I am using 4.5.1 and am trying to pre-compile a jsp file.
 Any ideas?
 I am using the following command line:
 java -classpath $CLASSPATH:$WEBLOGICCLASSPATH
 -Dweblogic.class.path=$WEBLOGICCLASSPATH weblogic.jspc 100-Welcome.jsp
 I have also tried the above command w/ -classpath $CLASSPATH
 Thanks,
 Richard
 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)

Hi again,
it turns out that the application outputs the above error if I run it from anywhere except EditPlus (what I use to code my applications - not an IDE), i.e. if I run the main class file from the command line, the same thing happens.
AAAAAHHHHH!!!!!

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

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

Memory maxed out when running weblogic 4.5

I am the tech support guy for my office, but I am WebLogic illiterate. I have a user who is running WebLogic, but when he runs it, his RAM and virtual memory max out. Are there any settings in WebLogic for memory allocation? Or is there a known problem with memory?

Please see my reply in misc.
Michael Girdley
Product Manager, WebLogic Server
BEA Systems Inc.
Jay A. Fulks <[email protected]> wrote in message
news:89gt0e$91a$[email protected]..
Hi.
I am running WebLogic 4.5.1.5 under Solaris 2.6. I am using JDK 1.2.2
with HotSpot. When we shutdown our server, it essentially crashes with
the following error:
# HotSpot Virtual Machine Error, Unexpected Signal 11
# Error happened during: mark sweep
# Error ID: 4F533F534F4C415249530E4350500BC2 01
After looking into the problem, we found that it is easily recreatable,
simply
by (1) starting the server, (2) hitting any web page (which causes
FileServlet
to be loaded), and (3) shutting down the server.
I have attached a tail of my log file as evidence.
Anybody else seen this problem? Is it a Weblogic/HotSpot compatibility
problem?
Thanks.

Error when running weblogic.appc

We have been running weblogic.appc for quite some time for precompiling our war-files. A few days ago we have been getting errors when precompiling one of our applications (it worked fine just a week ago). We build the war files using the same build setup.
We run the precompilation using the following command:
MW_HOME=/opt/lf/weblogic/wls1035_dev
java -classpath $MW_HOME/wlserver/server/lib/weblogic.jar:$MW_HOME/wlserver/server/lib/wlclient.jar weblogic.appc -verbose -verboseJavac -nowarn -k -maxfiles $2 -output $OUTPUT_HOME/$WAR_FILE-$WAR_END $WAR_HOME/$WAR_FILE*
The error we are getting is:
java.util.zip.ZipException: error in opening zip file
 at java.util.zip.ZipFile.open(Native Method)
 at java.util.zip.ZipFile.<init>(ZipFile.java:127)
 at java.util.zip.ZipFile.<init>(ZipFile.java:144)
 at weblogic.jsp.internal.Jar.<init>(Jar.java:24)
 at weblogic.jsp.internal.Application.createJavelinFile(Application.java:185)
 at weblogic.jsp.internal.CPL.initializeBinaryPaths(CPL.java:234)
 at weblogic.servlet.jsp.JspCLLManager.initPaths(JspCLLManager.java:437)
 at weblogic.servlet.jsp.JspCLLManager.initialize(JspCLLManager.java:237)
 at weblogic.servlet.jsp.JspCLLManager.<init>(JspCLLManager.java:228)
 at weblogic.servlet.jsp.JspCLLManager.<init>(JspCLLManager.java:221)
 at weblogic.servlet.jsp.JspCLLManager.compileJsps(JspCLLManager.java:126)
 at weblogic.servlet.jsp.jspc20.runBodyInternal(jspc20.java:454)
 at weblogic.servlet.jsp.jspc20.runJspc(jspc20.java:227)
 at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:236)
 at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:376)
 at weblogic.application.compiler.WARModule.compile(WARModule.java:245)
 at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
 at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
 at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
 at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
 at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:29)
 at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
 at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
 at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
 at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
 at weblogic.application.compiler.Appc.runBody(Appc.java:203)
 at weblogic.utils.compiler.Tool.run(Tool.java:158)
 at weblogic.utils.compiler.Tool.run(Tool.java:115)
 at weblogic.application.compiler.Appc.main(Appc.java:262)
 at weblogic.appc.main(appc.java:14)
And then for every jsp in the war file we are getting this error:
Exception encountered while compiling /tmp/appcgen_1316596871973_application.war/jspview/view.jsp
java.lang.NullPointerException
 at weblogic.jsp.internal.jsp.JspParser.jspParse(JspParser.java:1092)
 at weblogic.jsp.internal.jsp.JspParser._parse(JspParser.java:604)
 at weblogic.jsp.internal.jsp.JspParser.parse(JspParser.java:597)
 at weblogic.jsp.internal.jsp.JspAnalyzer.parseFile(JspAnalyzer.java:104)
 at weblogic.jsp.internal.jsp.JspAnalyzer.parse(JspAnalyzer.java:92)
 at weblogic.jsp.internal.ProxySourceFile.parse(ProxySourceFile.java:106)
 at weblogic.jsp.internal.SourceFile.getAst(SourceFile.java:559)
 at weblogic.jsp.internal.SourceFile.getAst(SourceFile.java:533)
 at weblogic.jsp.internal.SourceFile.check(SourceFile.java:335)
 at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:224)
 at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
 at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
 at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
 at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
At the end we are also getting the following output (I have checked the ownership and permissions and they are the same as for the applications that we get successful compilations).
There are 1 nested errors:
java.lang.RuntimeException: Error enumerating directory "/tmp/.jspcgen_1316596885663/war"; please check its ownership and permissions.
 at weblogic.utils.FileUtils.remove(FileUtils.java:299)
 at weblogic.utils.FileUtils.remove(FileUtils.java:316)
 at weblogic.application.io.ExplodedJar.remove(ExplodedJar.java:262)
 at weblogic.servlet.internal.War.remove(War.java:278)
 at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:249)
 at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:376)
 at weblogic.application.compiler.WARModule.compile(WARModule.java:245)
 at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
 at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
 at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
 at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
 at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:29)
 at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
 at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
 at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
 at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
 at weblogic.application.compiler.Appc.runBody(Appc.java:203)
 at weblogic.utils.compiler.Tool.run(Tool.java:158)
 at weblogic.utils.compiler.Tool.run(Tool.java:115)
 at weblogic.application.compiler.Appc.main(Appc.java:262)
 at weblogic.appc.main(appc.java:14)

We solved this by increasing the number of open files, by adding the following in the /etc/security/limits.conf
* soft nofile 50000
* hard nofile 50000

"Product is not installed" message when running weblogic upgrade installer

Hi,
I have successfully installed WLS 10.3.5 and JDeveloper Studio using jdevstudio11116install.jar installer on my local machine running Windows 7 64-bit Enterprise Edition . Now when I try upgrading WLS to version *10.3.6*, using wls1036_upgrade_generic.jar, I run into "*Product is not installed*" message. I tried even running wls1036_upgrade_win32.exe and the results are the same.
Appreciate if someone could tell me what I am doing wrong. I only followed the WLS install/upgrade documentation but looks like something is amiss.
Thanks.

Hi,
Appreciate if anybody out there can help me with the problem. I am wondering if the message cropped up due to the fact that I am trying to run a product upgrade specifically targeted at WebLogic Server instead of running a upgrade installer for jdeveloper since WLS 10.3.5 came with JDev installer in the first place. I am not aware if upgrade installlers are available for jdevstudio. Another way to put this is, I should have run WLS 10.3.5 installer first(instead of jdev) and the 10.3.6 upgrade installer next. That probably might have worked. Then again I am not sure this is correct.
Appreciate any help on this.
Thanks

Error when running weblogic 10 in cluster

I am testing out weblogic 10 and when I run it with a single managed server and an admin server then everything works fine. When I run it in a cluster with a valid test cluster license, I get the following error. Does anyone know what the cause of this error is and how to fix it? Thanks for the help.
 <Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
 java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
 java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
 at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
 at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
 at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
 at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
 at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
 at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
 at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
 at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
 at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
 at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
 at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
 at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
 at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
 at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
 at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
 at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
 at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
 at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
 at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
 at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
 at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
 at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
 at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 >

We solved this by increasing the number of open files, by adding the following in the /etc/security/limits.conf
* soft nofile 50000
* hard nofile 50000

Java.lang.NullPointerException when running weblogic on linux

Hi,
I installed the generic release of the Oracle WebLogic (wls1033_generic.jar) on my server (Ubuntu 64bit). When starting the application I am getting the following java exception. Is this a bug?
<Jun 22, 2010 9:29:51 AM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.deploy.internal.adminserver.DeploymentManager.getPendingDeploymentsForEditLockOwner(DeploymentManager.java:360)
at weblogic.management.provider.internal.EditAccessImpl.removePendingUpdateTasks(EditAccessImpl.java:560)
at weblogic.management.provider.internal.EditAccessImpl.undoUnsavedChanges(EditAccessImpl.java:555)
at weblogic.management.provider.internal.EditAccessImpl.acquireLock(EditAccessImpl.java:264)
at weblogic.management.provider.internal.EditAccessImpl.startEdit(EditAccessImpl.java:289)
Truncated. see log file for complete stacktrace
>
<Jun 22, 2010 9:29:51 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 22, 2010 9:29:51 AM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 22, 2010 9:29:51 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Are you running the process as the user that installed WebLogic and have write permissions in the domain directory?
How did you create the domain?

Error received when running weblogic in cluster

I am trying out clusters to see what the benefit would be to our application but I keep getting an error in the background. I have obtained a test cluster license and it is loading it up on startup. Does anyone know what this error is or how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

I am trying out clusters to see what the benefit would be to our application but I keep getting an error in the background. I have obtained a test cluster license and it is loading it up on startup. Does anyone know what this error is or how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

BeanAlreadyExistsException: Bean already exists when run weblogic.appc

We use weblogic.appc to generate the ejb jar file. It works fine on my Windows XP, but failed on another Windows XP. Below is the stack trace of the error message:
<Mar 17, 2009 8:49:27 AM PDT> <Error> <J2EE> <BEA-160197> <Unable to load descri
ptor D:\VSS\Client_Manager\bin\std-web-matrixejb.jar/META-INF/ejb-jar.xml of module std-web-matrixejb.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
at weblogic.application.descriptor.AbstractDescriptorLoader2.
getDescriptorBeanFromReaderAbstractDescriptorLoader2.java:774)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
at weblogic.ejb.spi.EjbJarDescriptor.getEjbJarBean(EjbJarDescriptor.java:131)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXM
LWithSchema(EjbDescriptorReaderImpl.java:671)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXML(EjbDescriptorReaderImpl.java:220)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyD
escriptorFromJarFile(EjbDescriptorReaderImpl.java:185)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.ejbc.EJBCompiler.parseDescriptors(EJBCompiler.java:1430)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:467)
at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:298)
at weblogic.application.compiler.EJBModule.compile(EJBModule.java:83)
at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:16)
at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:31)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:25
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:118)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:172)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:183)
at weblogic.appc.main(appc.java:14)
Caused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsExcept
ion: Bean already exists: "weblogic.j2ee.descriptor.SessionBeanBeanImpl@3eb8f669
(//Sessions[<!DOCTYPE ejb-jar PUBLIC '-..Sun Microsystems, Inc...DTD Enterprise
JavaBeans 2.0..EN' 'http:..java.sun.com.dtd.ejb-jar_2_0.dtd'> <ejb-jar> <enterpr
ise-beans> <session> <ejb-name>com.matrix.clientmanager.ejb.LoginDocHome<.ejb-na
me> <home>com.matrix.clientmanager.ejb.LoginEjbHome<.home> <remote>com.matrix.cl
ientmanager.ejb.LoginEjbRemoteIf<.remote> <ejb-class>com.matrix.clientmanager.ej
b.LoginEjb<.ejb-class> <session-type>Stateless<.session-type> <transaction-type>
Bean<.transaction-type> <.session> <session> <ejb-name>com.matrix.clientmanager.
ejb.GroupMaintenanceDocHome<.ejb-name> <home>com.matrix.clientmanager.ejb.GroupM
aintenanceEjbHome<.home> <remote>com.matrix.clientmanager.ejb.GroupMaintenanceEj
bRemoteIf<.remote> <ejb-class>com.matrix.clientmanager.ejb.GroupMaintenanceEjb<.
ejb-class> <session-type>Stateless<.session-type> <transaction-type>Bean<.transa
ction-type> <.session> <session> <ejb-name>com.matrix.clientmanager.ejb.StatusTr
eeDocHome<.ejb-name> <home>com.matrix.clientmanager.ejb.StatusTreeEjbHome<.home>
<remote>com.matrix.clientmanager.ejb.StatusTreeEjbRemoteIf<.remote> <ejb-class>
com.matrix.clientmanager.ejb.StatusTreeEjb<.ejb-class> <session-type>Stateless<.
session-type> <transaction-type>Bean<.transaction-type> <.session> <session> <ej
b-name>com.matrix.clientmanager.ejb.ChangeStatusDocHome<.ejb-name> <home>com.mat
rix.clientmanager.ejb.ChangeStatusEjbHome<.home> <remote>com.matrix.clientmanage
r.ejb.ChangeStatusEjbRemoteIf<.remote> <ejb-class>com.matrix.clientmanager.ejb.C
hangeStatusEjb<.ejb-class> <session-type>Stateless<.session-type> <transaction-t
ype>Bean<.transaction-type> <.session> <session> <ejb-name>com.matrix.clientmana
ger.ejb.EmployeeDocHome<.ejb-name> <home>com.matrix.clientmanager.ejb.EmployeeEj
bHome<.home> <remote>com.matrix.clientmanager.ejb.EmployeeEjbRemoteIf<.remote> <
ejb-class>com.matrix.clientmanager.ejb.EmployeeEjb<.ejb-class> <session-type>Sta
teless<.session-type> <transaction-type>Bean<.transaction-type> <.session> <sess
ion> <ejb-name>com.matrix.clientmanager.ejb.RoleScreenMappingDocHome<.ejb-name>
<home>com.matrix.clientmanager.ejb.RoleScreenMappingEjbHome<.home> <remote>com.m
atrix.clientmanager.ejb.RoleScreenMappingEjbRemoteIf<.remote> <ejb-class>com.mat
rix.clientmanager.ejb.RoleScreenMappingEjb<.ejb-class> <session-type>Stateless<.
session-type> <transaction-type>Bean<.transaction-type> <.session> <session> <ej
b-name>com.matrix.clientmanager.ejb.StatusLibraryDocHome<.ejb-name> <home>com.ma
trix.clientmanager.ejb.StatusLibraryEjbHome<.home> <remote>com.matrix.clientmana
ger.ejb.StatusLibraryEjbRemoteIf<.remote> <ejb-class>com.matrix.clientmanager.ej
b.StatusLibraryEjb<.ejb-class> <session-type>Stateless<.session-type> <transacti
on-type>Bean<.transaction-type> <.session> <session> <ejb-name>com.matrix.client
manager.ejb.LetterGroupDocHome<.ejb-name> <home>com.matrix.clientmanager.ejb.Let
terGroupEjbHome<.home> <remote>com.matrix.clientmanager.ejb.LetterGroupEjbRemote
If<.remote> <ejb-class>com.matrix.clientmanager.ejb.LetterGroupEjb<.ejb-class> <
session-type>Stateless<.session-type> <transaction-type>Bean<.transaction-type>
<.session> <session> <ejb-name>com.matrix.clientmanage])"
at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty
.setValue(RuntimeBindingType.java:483)
at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRunti
meProperty.fillCollection(AttributeRuntimeBindingType.java:385)
at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalOb
jectFromIntermediary(AttributeRuntimeBindingType.java:145)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElemen
tProperty(LiteralUnmarshalResult.java:159)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillE
lementProp(LiteralUnmarshalResult.java:130)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents
(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoInt
ermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(U
nmarshalResult.java:184)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
... 33 more
Edited by: [email protected] on Mar 17, 2009 10:25 AM

This exception is caused due to duplicate entries of the bean (TaskServiceBean) in CompositeServices\OrderApprovalHumanTask\public_html\WEB-INF\weblogic.xml file in WebLogicFusionOrderDemo project. Replace this file with the original one in the downloaded project zip and the application deploys successfully.

ExceptionInInitializer when running Jar

Hi,
I have developed an application which uses jdk1.4,jai and 2 classes from the jai demo classes. My application does not work when I create a jar however it does otherwise. I have included the jai_codec.jar and jai_core.jar classes in my jar. When my jar is run I get the following error:
Exception in thread "main" java.lang.ExceptionInInitializerError
<...>
Caused by: java.lang.RunTimeException: Registry intialization file not found.
at javax.media.jai.OperationRegistry.initializeRegistry(OperationRegistry.java:363)
Any help is much appreciated!!!!

Hi again,
it turns out that the application outputs the above error if I run it from anywhere except EditPlus (what I use to code my applications - not an IDE), i.e. if I run the main class file from the command line, the same thing happens.
AAAAAHHHHH!!!!!

Undefined weblogic.home error when running APPC

Hi,
I am trying to run the APPC compiler on my local EAR and deploy it on a remote
server version
8.1 using ANT. I just have the weblogic.jar, ojdbc14.jar and webservices.jar on
my workstation.
I have an error when running APPC.
The ANT taks is :
<target name="app.appc">
<java classname="weblogic.appc" fork="true" failonerror="true">
<jvmarg value="-Xms256m"/>
<jvmarg value="-Xmx256m"/>
<classpath>
<pathelement location="${j2ee.weblogic.lib.dir}/${j2ee.weblogic.lib.name}"/>
<pathelement location="${j2ee.weblogic.lib.dir}/ojdbc14.jar"/>
 <pathelement location="${jsdk1.4-dir}/lib/tools.jar"/>
 </classpath>
 <arg line ="-verbose -verboseJavac ${application.dist.ear}"/>
</java>
</target>
The ANT output is :
app.appc:
[java] [appc] Created working directory: C:\DOCUME~1\pim\LOCALS~1\Temp\appcgen
[java] [appc] Compiling EAR module 'core.war'
[java] [JspcInvoker]Checking web app for compliance.
[java] <2 mars 2004 15 h 36 CET> <Info> <HTTP> <BEA-101047> <[ComplianceChecker]
Validating the servlet element with servlet-name named "action".>
[java] <2 mars 2004 15 h 36 CET> <Info> <HTTP> <BEA-101047> <[ComplianceChecker]
Checking servlet-mapping for servlet name : "action".>
[java] [jspc] parsing /jsp/applications/example/Accessor.jsp:
[java] [jspc] parsed C:\DOCUME~1\pim\LOCALS~1\Temp\appcgen\appcgen_core.war\
jsp\applications\example\Accessor.jsp in 1482 ms.
[java] [jspc] Invoking the compiler
[java] [jspc] Invoking the compiler with -encoding UTF-8
[java] [appc] Compiling EAR module 'core-ejb.jar'
[java] [J2EE:160121]Errors encountered while compiling module 'core-ejb.jar':
[java] error in finding weblogic.Home
Is there any other solution than installing weblogic on my workstation so that
everything is
setup correctly?
thanks in advance
Pierre

Pierre MONGENIE wrote:
Finally it worked out for me with the system classpath set to:
D:\J2EE\bea\weblogic81\server\lib\weblogic.jar
and the ANT task wlappc.
I was unable to have it work with the ANT task described below in this thread.
tha ant task is
<wlappc source="${application.dist.ear}"
 verbose="true"
 verboseJavac="true"
 debug="true"
 classpath="${j2ee.weblogic.lib.dir}/${j2ee.weblogic.lib.name}
 ${j2ee.weblogic.lib.dir}/ojdbc14.jar
 ${j2ee.weblogic.lib.dir}/webservices.jar
 ${jsdk1.4-dir}/lib/tools.jar"This is the issue. The classpath parameter to wlappc is the classpath
it will use when it compiles your application classes. It's not the
classpath which will load the wlappc ant task. (I'll admit this has
always been confusing.)
-- Rob
runtimeflags="mx256m"
output="${application.weblogic.deploy.ear}"
 />
So now I have another problem but let me open another thread
thanks
Rob Woollen <[email protected]> wrote:
That code checks if the system property weblogic.home is set. If not,
it looks for the class weblogic.Home is in the classpath. Make sure
one
of those 2 conditions is true.
-- Rob
Pierre MONGENIE wrote:
Hi,
I am trying to run the APPC compiler on my local EAR and deploy iton a remote
server version
8.1 using ANT. I just have the weblogic.jar, ojdbc14.jar and webservices.jaron
my workstation.
I have an error when running APPC.
The ANT taks is :
<target name="app.appc">
<java classname="weblogic.appc" fork="true" failonerror="true">
<jvmarg value="-Xms256m"/>
<jvmarg value="-Xmx256m"/>
<classpath>
<pathelement location="${j2ee.weblogic.lib.dir}/${j2ee.weblogic.lib.name}"/>
<pathelement location="${j2ee.weblogic.lib.dir}/ojdbc14.jar"/>
 <pathelement location="${jsdk1.4-dir}/lib/tools.jar"/>
 </classpath>
 <arg line ="-verbose -verboseJavac ${application.dist.ear}"/>
</java>
</target>
The ANT output is :
app.appc:
[java] [appc] Created working directory: C:\DOCUME~1\pim\LOCALS~1\Temp\appcgen
[java] [appc] Compiling EAR module 'core.war'
[java] [JspcInvoker]Checking web app for compliance.
[java] <2 mars 2004 15 h 36 CET> <Info> <HTTP> <BEA-101047> <[ComplianceChecker]
Validating the servlet element with servlet-name named "action".>
[java] <2 mars 2004 15 h 36 CET> <Info> <HTTP> <BEA-101047> <[ComplianceChecker]
Checking servlet-mapping for servlet name : "action".>
[java] [jspc] parsing /jsp/applications/example/Accessor.jsp:
[java] [jspc] parsed C:\DOCUME~1\pim\LOCALS~1\Temp\appcgen\appcgen_core.war\
jsp\applications\example\Accessor.jsp in 1482 ms.
[java] [jspc] Invoking the compiler
[java] [jspc] Invoking the compiler with -encoding UTF-8
[java] [appc] Compiling EAR module 'core-ejb.jar'
[java] [J2EE:160121]Errors encountered while compiling module'core-ejb.jar':
[java] error in finding weblogic.Home
Is there any other solution than installing weblogic on my workstationso that
everything is
setup correctly?
thanks in advance
Pierre

Exception when run popup page in weblogic

Hi all,
I am using Jdeveloper 11.1.1.1.0 and weblogic standalone 10.3.1.0
I created web app with popup page, I defined outcome of popup page in adfc-config.xml, It is OK when run in Jdeveloper. Popup page is opened.
I installed ADF framework for weblogc. I created a new domain for weblogic
I created connection to weblogic and deploy webapp to weblogic from Jdeveloper.
When I call 1 normal page, click 1 button for open popup then Exception raise:
javax.servlet.ServletException: java.lang.NoClassDefFoundError: oracle/adf/controller/security/TaskFlowPermission
I do not know why.
Please help me
Duy

Dear Timo,
I installed all libraries for weblogic
But TaskFlowPermission is a class of Jdeveloper 11.1.1.0.1. it is in package adf-controller.jar
While I an using Jdeveloper 11.1.1.1.0 for develop, In adf-controller.jar of Jdeveloper 11.1.1.1.0 there is not TaskFlowPermission class.
Duy

Weblogic jspc

Hi,
Version: Weblogic 8.1 SP3.
OS: Sun Solaris.
I have a requirement wherein I need to be able to compile a jsp as part of a batch job. I read the docs at http://e-docs.bea.com/wls/docs81/jsp/reference.html#65756/ and was hoping to use the java weblogic.jspc command.
However I am always thrown the "Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/jspc".
I am not certain what I am doing wrong. Would appreciate any help. Do I have to modify the CLASSPATH settings in startweblogic.sh for this?
One other question. (this I can answer by trial and error if I get the answer to above..)
Do I have to include the CLASSPATH which I have already specified in startweblogic.sh when I use the java weblogic.jspc command?
Thanks a ton.
Shikhar

It's me again... Now I am running into a different issues... have posted the command executed and the output.. Any help is appreciated...
Thanks
Shikhar
C:\bea\user_projects\domains\demodomain>java -Dweblogic.jsp.windows.caseSensitiv
e=true -classpath C:\bea\weblogic81\server\lib\weblogic.jar; weblogic.jspc -verb
oseJspc C:\bea\user_projects\domains\demodomain\demo\stage\Vignette_Portal\porta
l.war\global1\jsp\alertsEmail.jsp
[jspc] warning: expected file /WEB-INF/web.xml not found, tag libraries cannot
be resolved.
<Oct 20, 2005 12:10:56 PM CDT> <Warning> <HTTP> <BEA-101181> <Could not find web
.xml under WEB-INF in the doc root: ..>
[jspc] parsing /demo/stage/Vignette_Portal/portal.war/global1/jsp/alertsEmail.js
p:
[jspc] parsed .\demo\stage\Vignette_Portal\portal.war\global1\jsp\alertsEmail.js
p in 1002 ms.
[jspc] generated java file C:\bea\user_projects\domains\demodomain\__alertsEmail
.java
[jspc] Invoking the compiler with -encoding UTF-8
Compiler class: 'com.sun.tools.javac.Main', not found
java.lang.ClassNotFoundException: com.sun.tools.javac.Main
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvo
ker.java:406)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:
328)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:
336)
at weblogic.jspc.doCompile(jspc.java:823)
at weblogic.jspc.runJspc(jspc.java:632)
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)
Error: [jspc]: 0 file(s) failed:
Exception in thread "main"
[Compilation errors : ]
at weblogic.jspc.doCompile(jspc.java:839)
at weblogic.jspc.runJspc(jspc.java:632)
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)
java.lang.Exception: [Compilation errors : ]
at weblogic.jspc.doCompile(jspc.java:842)
at weblogic.jspc.runJspc(jspc.java:632)
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)
C:\bea\user_projects\domains\demodomain>

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?

ExceptionInInitializer when running weblogic.jspc

Similar Messages

Maybe you are looking for