Weblogic MBeanMaker and Sun JDK 1.4.2
I just upgraded the JVM in my development environment to 1.4.2_04 and
the Weblogic MBeanMaker no longer works.
Has anyone seen this?
The configuration is as follows:
WLS 8.1 SP2
JDK 1.4.2_04
Windows 2000
The build script is Ant driven and I verified that if I return to
1.4.1_06 it works fine and the MBean jar file is created.
Here is the relevant xml file from the Ant script and the error that I get:
<target name="build.mjf" depends="init">
<echo message="Generating MJF file: ${mjf}"/>
<java classname="weblogic.management.commo.WebLogicMBeanMaker"
fork="true" failonerror="true">
<jvmarg line="-Dfiles=${mfiles} -DMJF=${mjf} -DcreateStubs=true"/>
<classpath>
<pathelement path="${classpath}"/>
<pathelement location="${build_dir}"/>
<pathelement location="${WEBLOGIC}"/>
</classpath>
<arg value="-g"/>
<arg value="-verbose"/>
</java>
</target>
build.mjf:
[echo] Generating MJF file: X:/release/CustomWeblogicProviders.jar
[java] Compiling the files...
[java] About to compile with arguments:
[java] -g -d X:/release/lib/build_mb
[java] javac: no source files
[java] Usage: javac <options> <source files>
[java] where possible options include:
[java] -g Generate all debugging info
[java] -g:none Generate no debugging info
[java] -g:{lines,vars,source} Generate only some debugging info
[java] -nowarn Generate no warnings
[java] -verbose Output messages about what the
compiler is doing
[java] -deprecation Output source locations where
deprecated APIs are used
[java] -classpath <path> Specify where to find user class
files
[java] -sourcepath <path> Specify where to find input
source files
[java] -bootclasspath <path> Override location of bootstrap
class files
[java] -extdirs <dirs> Override location of installed
extensions
[java] -d <directory> Specify where to place generated
class files
[java] -encoding <encoding> Specify character encoding used
by source files
[java] Compiling these files (debug)Exec failed .. exiting
[java] -source <release> Provide source compatibility
with specified release
[java] -target <release> Generate class files for
specific VM version
[java] -help Print a synopsis of standard options
--dejan
I think, this is a bug between the jvm from Sun and the Ant Task because I have
tried without the Server, and I have not this problem.
I have tried with a lot of values, for exemple :
-Xms32m -Xmx200m
-Xms64m -Xmx200m
-Xms128m -Xmx200m
-Xms128m -Xmx128m
-Xms256m -Xmx256m
-Xms512m -Xmx512m
If the virtual machine need up than 512, there is a problem somewhere !!!
And I have not this problem with the previous version 1.4.1_05.
I have also tried with just the max value, -Xmx200m, I have no problem. And with
just the min value, I have the following message Too small initial heap, else
with 512.
This is impossible to have not enough memory with 512 MB.
How has you resolved your problem ???
Thanks for your help.
"Deyan D. Bektchiev" <[email protected]> wrote:
Sebastian,
Your problem might be much simpler than you think. Just set your minimum
heap size to be equal to the maximum and then try it again.
It could be that the minimum heap size allowed values was changed.
Regards,
Dejan
Seb wrote:
Hi Deyan,
We have almost the same problem with an ant task to start a WeblogicServer.
Our Ant Task starts any problem with the java version 1.4.1_05 but wehave the
same error message "Invalid initial heap size: -Xms32m -Xmx200m Couldnot create
the Java virtual machine." when we uses the java version 1.4.2.
Thanks help us to find a solution.
"Deyan D. Bektchiev" <[email protected]> wrote:
I just upgraded the JVM in my development environment to 1.4.2_04 and
the Weblogic MBeanMaker no longer works.
Has anyone seen this?
The configuration is as follows:
WLS 8.1 SP2
JDK 1.4.2_04
Windows 2000
The build script is Ant driven and I verified that if I return to
1.4.1_06 it works fine and the MBean jar file is created.
Here is the relevant xml file from the Ant script and the error that
I get:
<target name="build.mjf" depends="init">
<echo message="Generating MJF file: ${mjf}"/>
<java classname="weblogic.management.commo.WebLogicMBeanMaker"
fork="true" failonerror="true">
<jvmarg line="-Dfiles=${mfiles} -DMJF=${mjf} -DcreateStubs=true"/>
<classpath>
<pathelement path="${classpath}"/>
<pathelement location="${build_dir}"/>
<pathelement location="${WEBLOGIC}"/>
</classpath>
<arg value="-g"/>
<arg value="-verbose"/>
</java>
</target>
build.mjf:
[echo] Generating MJF file: X:/release/CustomWeblogicProviders.jar
[java] Compiling the files...
[java] About to compile with arguments:
[java] -g -d X:/release/lib/build_mb
[java] javac: no source files
[java] Usage: javac <options> <source files>
[java] where possible options include:
[java] -g Generate all debugging info
[java] -g:none Generate no debugging info
[java] -g:{lines,vars,source} Generate only some debugging
info
[java] -nowarn Generate no warnings
[java] -verbose Output messages about what the
compiler is doing
[java] -deprecation Output source locations where
deprecated APIs are used
[java] -classpath <path> Specify where to find user class
files
[java] -sourcepath <path> Specify where to find input
source files
[java] -bootclasspath <path> Override location of bootstrap
class files
[java] -extdirs <dirs> Override location of installed
extensions
[java] -d <directory> Specify where to place generated
class files
[java] -encoding <encoding> Specify character encoding used
by source files
[java] Compiling these files (debug)Exec failed .. exiting
[java] -source <release> Provide source compatibility
with specified release
[java] -target <release> Generate class files for
specific VM version
[java] -help Print a synopsis of standard
options
--dejan
Similar Messages
-
Weblogic Producer and Sun Portal as Consumer
Hi,
I am trying to have Weblogic 8.1SP4 as a producer and Sun Portal 2005Q1 as consumer.
I have deployed my JSR 168 compliant portlet application on Weblogic. When i try 2 register a WSRP consumer in Sun Portal using the WSDL URL generated by Weblogic it throws a
java.io.FileNotFoundException: http://hostip:port/TestPortalProject/wlp_wsrp_v1_bindings.wsdl.
Any suggestions on why such an exception is thrown?
Regards,
MuktaThis is a known issue. The work-around is to deploy copy the imported
files from wsrp-common.jar's schema/src dir to the root of your webapp.
Subbu
Mukta Shetye wrote:
Hi,
I am trying to have Weblogic 8.1SP4 as a producer and Sun Portal 2005Q1 as consumer.
I have deployed my JSR 168 compliant portlet application on Weblogic. When i try 2 register a WSRP consumer in Sun Portal using the WSDL URL generated by Weblogic it throws a
java.io.FileNotFoundException: http://hostip:port/TestPortalProject/wlp_wsrp_v1_bindings.wsdl.
Any suggestions on why such an exception is thrown?
Regards,
Mukta -
SQL Developer 1.5.1 and Sun JDK 1.6 Update 10
Now that the long-awaited Update 10 went FCS, SQL Developer doesn't complain that it's unsupported, it accepts to start normally. Unfortunately, it seems that SQL Developer is not perfectly compatible with the new JDK: if you open a table and click in the 'Data' tab, nothing happens. The Log window doesn't show any error, there are no other probems, if I click other tabs they work, but of course the Data tab is essential for daily work. I have to go back to JDK 6u7 or 5_16. Platform is Windows Vista SP1.
Hi there, I also have Windows XP SP3 and java sdk 6 u10 installed.
If I try to start the sql developer following exception is raised (so the splash screen appears and then the ide crashes):
oracle.javatools.util.ClosureException: java.lang.ClassCastException: oracle.ideimpl.plaf.WindowsComboBoxUI$MarginBorderTextField cannot be cast to javax.swing.JComboBox
at oracle.javatools.util.SwingClosure.run(SwingClosure.java:83)
at oracle.ideimpl.MainWindowImpl.postInitialize(MainWindowImpl.java:701)
at oracle.ide.IdeCore.startupImpl(IdeCore.java:1515)
at oracle.ide.Ide.startup(Ide.java:662)
at oracle.ideimpl.DefaultIdeStarter.startIde(DefaultIdeStarter.java:35)
at oracle.ideimpl.Main.start(Main.java:110)
at oracle.ideimpl.Main.main(Main.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.ide.boot.PCLMain.callMain(PCLMain.java:66)
at oracle.ide.boot.PCLMain.main(PCLMain.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.classloader.util.MainClass.invoke(MainClass.java:128)
at oracle.ide.boot.IdeLauncher.bootClassLoadersAndMain(IdeLauncher.java:190)
at oracle.ide.boot.IdeLauncher.launchImpl(IdeLauncher.java:90)
at oracle.ide.boot.IdeLauncher.launch(IdeLauncher.java:66)
at oracle.ide.boot.IdeLauncher.main(IdeLauncher.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.ide.boot.Launcher.invokeMain(Launcher.java:729)
at oracle.ide.boot.Launcher.launchImpl(Launcher.java:115)
at oracle.ide.boot.Launcher.launch(Launcher.java:68)
at oracle.ide.boot.Launcher.main(Launcher.java:57)
Caused by: java.lang.ClassCastException: oracle.ideimpl.plaf.WindowsComboBoxUI$MarginBorderTextField cannot be cast to javax.swing.JComboBox
at oracle.ideimpl.plaf.WindowsComboBoxUI$PropertyChangeHandler.propertyChange(WindowsComboBoxUI.java:259)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276)
at java.awt.Component.firePropertyChange(Component.java:7961)
at javax.swing.JComponent.addNotify(JComponent.java:4684)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at oracle.ideimpl.docking.TitledPanel.addNotify(TitledPanel.java:259)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at java.awt.Container.addNotify(Container.java:2560)
at javax.swing.JComponent.addNotify(JComponent.java:4683)
at javax.swing.JRootPane.addNotify(JRootPane.java:735)
at java.awt.Container.addNotify(Container.java:2560)
at java.awt.Window.addNotify(Window.java:645)
at java.awt.Frame.addNotify(Frame.java:470)
at oracle.ideimpl.MainWindowImpl.addNotify(MainWindowImpl.java:613)
at java.awt.Window.show(Window.java:841)
at java.awt.Component.show(Component.java:1447)
at java.awt.Component.setVisible(Component.java:1400)
at java.awt.Window.setVisible(Window.java:824)
at oracle.ideimpl.MainWindowImpl$6.runImpl(MainWindowImpl.java:756)
at oracle.javatools.util.SwingClosure$1Closure.run(SwingClosure.java:50)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) -
How to identify the installed Weblogic Server and JDK are 32bit or 64bit?
Hi everyone,
I have a question ~
Both Weblogic Server and JAVA JDK are installed on the server already, but I only know the Weblogic Server is 10.3.4.0 and JAVA JDK version is 1.6.0_25.
I know the 64bit Weblogic Server installation file is a wlsXXXX_generic.jar package and 64bit JAVA JDK needed also.
But, since the Weblogic installed already, there are no such installation files on the Linux Server now.
I have tried the "java -version" for java version and check the Weblogic version from Weblogic console.
How to identify the installed Weblogic Server and JDK are 32bit or 64bit with Linux command? Or is there any way to check it?What you can try to do is use WLST (or an MBean browser, such as JConsole or JRockit Mission Control) and connect to the adminserver.
For example when using WLST:
# set the environment by using setWLSEnv.sh (located in the ${WL_HOME}/server/bin directory).
# start WLST by using: java weblogic.WLST
# connect to the adminserver
connect('adminusername','adminpassword');
# change to the serverruntime environment
serverRuntime();
# show the attributes
ls();
# Here an attribute is shown called WebLogicVersion that shows the version of WebLogic
-r-- WeblogicVersion WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
# Note that this does not show if is 32 bits or 64 bits to retrieve this information you have obtain the JVM version
# change the directory
cd('JVMRuntime/AdminServer');
# show the attributes
ls();
-r-- Version R28.0.1-21-133393-1.6.0_20-20100512-2126-linux-x86_64
# when you have something like x86 at the you are running a 32 bit version, if you have something like x86_64 you are running a 64 bits versionAs mentioned above you can also retrieve this information by using a MBean browser. -
Can sun jdk 1.5 for webstart and sapjvm co-exist on the same server?
We just installed PI 7.1. We would like to install sun jdk 1.5 on the PI 7.1 server so we can use the pi tools on the server, but we are not sure if sapjvm and sun jdk can co-exist, or if it's going to cause any problem with PI 7.1, any setting is needed to tell PI which java to use if multiple version is installed? Does anybody know?
Thanks
Jane ZhouKaushal,
Thanks for the reply. note 718901 mentioned to change the jdk version, parameter jstartup/vm/home in instance profile can be used. if that's the case, that should be how we tell PI system whch jdk to use? in PI 7.1, it's point to DIR_SAPJVM, which points to sapjvm_5 in \exe directory. The notes you mentioned all apply to versions before 7.1, I'm wondering if it still works the same way with 7.1 systems.
Has anybody installed a sun jdk on PI 7.1? anything that we need to pay attention to?
Thanks
Jane -
GC taking long time when using Concurrent Mark Sweep GC with Sun JDK 150_12
We are having problem of Garbage collection taking too long. We are using Weblogic 9.2 and Sun JDK 150_12
Below are the memory arguments we are using. We are using Concurrent Mark Sweep GC. What we are observing is Young Generation is getting filled up and consequent tenured generation also hangs with long pauses.
Below are the JVM arguments we are using
-Xms2560M -Xmx2560M -Xloggc:${LOGDIR}/gc.log -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 -XX:CMSInitiatingOccupancyFraction=60 -XX:NewSize=512m -XX:MaxNewSize=512m -XX:MaxPermSize=256m
I have seen many forums where there are many reported issues with Concurrent Mark Sweep garbage collection with Sun JDK, but with different recommendations. But did not find any defnite recommendation. Please advice.
- - TarunWe are having problem of Garbage collection taking too long. We are using Weblogic 9.2 and Sun JDK 150_12
Below are the memory arguments we are using. We are using Concurrent Mark Sweep GC. What we are observing is Young Generation is getting filled up and consequent tenured generation also hangs with long pauses.
Below are the JVM arguments we are using
-Xms2560M -Xmx2560M -Xloggc:${LOGDIR}/gc.log -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 -XX:CMSInitiatingOccupancyFraction=60 -XX:NewSize=512m -XX:MaxNewSize=512m -XX:MaxPermSize=256m
I have seen many forums where there are many reported issues with Concurrent Mark Sweep garbage collection with Sun JDK, but with different recommendations. But did not find any defnite recommendation. Please advice.
- - Tarun -
Uninstall SUN JDK 1.6_14 and install SUN JDK 1.6_18 for Weblogic
My GridControl server has all of a sudden gone wild in consuming 100% of the cpu. The process was java.exe in the Middleware folder. Somebody suggested to verify the JDK and I indeed have an older version than the one recommended.
Does anybody know where it is documented on how to uninstall and then reinstall SUN JDK 1.6_18 and have Weblogic still work afterward? (Win 2008 32 bit)
I'd hate to reinstall the entire Gridcontrol 11g because I have the wrong jdk.
Thanks.Hi,
Uninstalling SUN JDK 1.6_14 from your Box is optional step....Most of the Servers are flexible enough ...they provide us the facility to change the JDK at any point of time...Without reinstalling the Product from the scrap....
You can directly install SUN JDK 1.6_18 in your WebLogic Server Box. Then you need to make a small change in the *"<DOMAIN_HOME>\bin\setDomainEnv.cmd"* file ...to change the JAVA_HOME variable value...That's all.
Next time whenever you will start your WebLogic Servers it will pick up the SUN JDK 1.6_18 version only.
I am pasting few lines from *"setDomainEnv.cmd"*
@REM *************************************************************************
set WL_HOME=C:\bea103\wlserver_10.3
for %%i in ("%WL_HOME%") do set WL_HOME=%%~fsi
set BEA_JAVA_HOME=C:\bea103\jrockit_160_05
<b><font color=red>set SUN_JAVA_HOME=C:\all_Jdks\JDK 1.6_18</font></b>
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dwhat.is.your.name=Jay_SenSharma
if "%JAVA_VENDOR%"=="BEA" (
set JAVA_HOME=%BEA_JAVA_HOME%
) else (
if "%JAVA_VENDOR%"=="Sun" (
set JAVA_HOME=%SUN_JAVA_HOME%
) else (
set JAVA_VENDOR=Sun
set JAVA_HOME=C:\bea103\jdk160_05
@REM We need to reset the value of JAVA_HOME to get it shortened AND
@REM we can not shorten it above because immediate variable expansion will blank it
set JAVA_HOME=%JAVA_HOME%
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here) -
Java Generics in Ejbs WebLogic 9.2 MP1 WindowsXP Sun JDK
Hi guys,
I tried to deploy our application on Weblogic Server 9.2 MP1 (Windows, Sun JDK) and during deployment I have this error see bellow.
Can somebody tell me what is the problem with generics and EJB compiler?
Is necessary to add any path or change any server settings?
Thanks for help
Robert
location: interface
...daoadapter_DaoAdapter_rge4uk_Intf
public void batchPersist(java.util.List<T> arg0);
^
...daoadapter_DaoAdapter_rge4uk_Intf.java:20: cannot find symbol
symbol : class T
location: interface
2 errors
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
n.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:15
7)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
tReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
erCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
lbackDeliverer.java:45)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)Thanks Matt for your answer.
But I don't finish my testing :)
I tried to deploy the same application on Weblogic 9.2 MP2 and then MP3 (sun jdk domain) and I didn't have problem with generics (application was correctly deployed and running).
Then something was fixed in newer versions or may be bea guys support more then is in EJB 2.x specification.
My next step, I'll try to deploy it on Jrockit domain and I give a note to conference what happen, may be it can help to somebody else.
Thanks
Robert -
Duplicate soap envelope with JRockit and not Sun JDK
I have been installed Weblogic 10.3.6 with Sun JDK 1.6 on Windows 7 64 bit. This has worked great for a client sending in a soap request which is processed in my war as a 1.2 message. Debugging this shows the response is valid in my code, and works on Sun 1.6 fine.
When I switched to JRockit [jrockit-jdk1.6.0_33-R28.2.4-4.1.0-windows-x64] I started to receive a duplicate soap envelope and soap body wrapped around the valid soap envelope which worked before.
With the only change being switching to JRockit, this must be the cause of the addition of the duplicate the soap body and envelope. I searched this forum and Google and have not found a reason or solution.
Any ideas on a solution?Seems to be the case that using MTOM stops this problem with JRockit. Strange but apparently true (so far).
-
Weblogic 9.0 on WinXP 64bit with Sun JDK 64bit
I installed Weblogic 9.0 on WindowXP 64bit version and it's fine with build in Sun's JDK and JRockit JDK but as soon as I switch to Sun's 64bit implementation of JDK (update 5) it fails to start.
Am I doing something wrong or it is not compatible with 64bit JDK on windows platform?
If so are there any plans to make it compatible with Sun's JDK 64bit version on windows platform in the near future, or any chance of 64bit JRockit JDK for windows?On 07/20/2015 06:35 AM, Itzhak Hovav wrote:
> hi
> [snip]
> [root@p22 eclipse]# cat eclipse.ini -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807
>
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx512m
> [snip]
Try this: http://wiki.eclipse.org/Eclipse.ini. You should have read the
sticky posts at forum's top for getting started help. -
Difference between SUN JDK V1.4.2_05 and JDK V1.4.2_07
difference between SUN JDK V1.4.2_05 and JDK V1.4.2_07 and I want to the link in SUN for that. I want to know the bug fixes between them.
Perhaps you should look at the documentation which comes with JDK 1.4.2_08.
It has the bugs fixed listed. -
[SOLVED] Dependency problems Sun JDK, OpenJDK and Soprano
Hi there,
as I need the Sun JDK for programming, I wanted to replace OpenJDK with SunJDK. Here's what's happening:
schorsch@archie:~$ sudo pacman -S jdk
resolving dependencies...
looking for inter-conflicts...
:: jdk conflicts with openjdk6. Remove openjdk6? [Y/n] Y
error: failed to prepare transaction (could not satisfy dependencies)
:: jdk: requires jre
:: soprano: requires openjdk6
schorsch@archie:~$
What's the proper way to do this? Should I avoid having more than one java version installed on my machine? I guess so...
I'm doing quite a bit of java development and sometimes really need the latest Sun Java.
TIA,
Blackhole
Last edited by blackhole (2009-02-18 18:56:53)Okay guys, I did a "pacman -Rd openjdk6 && pacman -S jdk" which worked fine:
schorsch@archie:~$ java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode)
schorsch@archie:~$
However when I use Konqueror and go to http://www.java.com/en/download/help/testvm.xml in order to test my java version, it doesn't work.
More precisely the applet is not displayed at all. When I go to the Konqueror settings and to "Java & JavaScript", tick the checkbox "Use KIO" and refresh the page. I at least get a big gray square where the applet should be.
Do I have to install any additional java plugin? Is anybody out there using Konqueror with the Sun Jre?
//Edit: I've come across this: http://www.konqueror.org/javahowto/ but I was wondering whether this is already included in some Arch package. I don't wanna fiddle manually if there's a proper Arch way to do things.
TIA,
Blackhole
Last edited by blackhole (2009-02-18 13:58:17) -
Revision: 11488
Author: [email protected]
Date: 2009-11-05 17:10:10 -0800 (Thu, 05 Nov 2009)
Log Message:
Resubmitting binary distribution of xercesPatch.jar from the third party module in the SDK and compiled it with Sun JDK 1.4.2_12.
QE notes: N/A
Doc notes: N/A
Bugs:
SDK-16818 - Must open-source the code for xercesPatch.jar.
Reviewer: Discussed with Gordon
Tests run: Checkintests
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16818
Modified Paths:
flex/sdk/trunk/lib/xercesPatch.jar
flex/sdk/trunk/modules/thirdparty/xerces-patch/build.xmlDid you try this:
http://forum.java.sun.com/thread.jsp?thread=434718&forum=60&message=1964421 -
Different complining result between SUN JDK 1.4 and IBM JDK 1.3.1
Hi! I simplifed my code as following:
public class TestException2 {
public Object test() {
java.sql.Connection cn = null;
try {
// 1st. close
cn.close();
catch (java.sql.SQLException se) {
// 2nd. close
cn.close();
finally {
return new Object();
}But I get different compiling result betwueen SUN JDK 1.4.2 and IBM JDK 1.3.1 (I have to deploied my app to the websphere 5.0)
In Sun JDK 1.4.2, I only got a warning:
[e:\work\test]javac TestException2.java
TestException2.java:14: warning: finally clause cannot complete normally
^
1 warningIn IBM JDK 1.3.1, I got an error:
TestException2.java:10: unreported exception java.sql.SQLException; must be caught or declared to be
thrown
cn.close();
^
1 errorWhat happend? Who is right?
Thank you!
[ I believe the code should not pass the compilation ... ]Many other people agree with you, including some Sun engineers.
Perhaps Sun just feels an obligation to continue to allow it for legacy reasons.
You might also investigate the compiler that comes with Eclipse.
http://www.eclipse.org/
It has a more flexible approach: for some cases, it lets you decide what is a warning and what is an error. -
Weblogic 7.0 and Sun's sdk 1.4.1_01
I'm involved in a project which is composed of Weblogic application server
and later a rich Java client (Swing).
I dislike having a lot of Java sdk(s) on multiple places in my computer and
I wish to use the Java most recent version.
My questions are:
- Is Java sdk 1.4 supported on Weblogic 7?
- If not, do you have any experience/problems with it?
- In the worst case, I won't upgrade to the most recent Java version on the
server side.
What implications, if any, does this have on the rich client?
Should I use for client side development the same Java version as Weblogic
does or can I get by with 1.4?Why do you recommend 1.3.1_06, not 1.3.1_07? I just tried _07 (on WinXP) and I'm
not sure but I think the error I'm getting now about "libmuxer not found" didn't
happen with _06. Is that a known problem?
-greg.
"Wayne W. Scott" <[email protected]> wrote:
Oh Gawd, here we go again. Please don't yell at me like so many others
have done when
they get answers that they did not want to hear.
Java SDK 1.4 has NOT been certified with any BEA product yet. The plans
are for the
first one to be the Olympic release, probably to be called WLS 8.1, due
this Summer.
AFAIK, the biggest problems have been in the integration of Security
products with 1.4.
I do not know all the nitty-gritty details. The latest JDK I would
use is 1.3.1_06.
I have no further guidance on other related topics.
Best Wishes,
Wayne Scott
Yonatan Taub wrote:
I'm involved in a project which is composed of Weblogic applicationserver
and later a rich Java client (Swing).
I dislike having a lot of Java sdk(s) on multiple places in my computerand
I wish to use the Java most recent version.
My questions are:
- Is Java sdk 1.4 supported on Weblogic 7?
- If not, do you have any experience/problems with it?
- In the worst case, I won't upgrade to the most recent Java versionon the
server side.
What implications, if any, does this have on the rich client?
Should I use for client side development the same Java version asWeblogic
does or can I get by with 1.4?
Maybe you are looking for
-
XML Problem - Markup not well-formed? (kinda long)
Hello, I'm working on my first AIR app and I've run into a bit of a snag. The app is intended to allow users of our system to create a Word document, save it as XML, and then load it into the AIR app and have some manipulation performed to extract d
-
Revision: 10635 Author: [email protected] Date: 2009-09-28 06:49:45 -0700 (Mon, 28 Sep 2009) Log Message: Fixed FB issue with FXG in library projects. QE notes: Doc notes: Bugs: FB-22197 Reviewer: pfarland Cycloner: gcomnino Tests run: checkint
-
Need my 30" display to be 25ft away from our G5
Need my 30" display to be 25ft away from our G5 I'm not finding many solutions on how I can do this and still retain a high quality image. Do i need some sort of repeater? Not getting any answers from stores around here. Help!!!!
-
Can I generate .hlp files
We just upgraded to Frame 9 (from 7.1) and RoboHelp 8. Prior to the upgrade, I was using WebWorks to generate my .hlp files - is there a way to generate .hlp and .cnt files with RH8? Thanks in advance! Debby
-
After downloading the lastest update, IOS 6, my iphone will not download apps.
after downloading the lastest update, IOS 6, my iphone will not download apps. help