Vrml browsers that work with sun java in windows
Hi, i was wondering if anyone knew any good vrml browsers that worked with sun java in microsoft windows, I tried cortona but that only used microsoft's jvm which was discontinued and i wanted to avoid. I am currently trying to use cosmo player but am having troubles with it. Im specifically looking for good vrml api's that come with the browsers containing up to date available source code etc.
Thanks
Andy
Is there noone on this site that uses VRML?
Similar Messages
-
How can I make an icon that links to a webpage that works with Mac and Windows??
Hi!
I burn CDs with my photos and send them to clients. Besides the photos folder, I would like to include a file (similar to the .webloc files on the Mac Desktop) that can be clicked and it will be linked to my website - it will open up a browser window and go to my website . Is it posssible to make one of these icons that works with both Macs and Windows machines? Thanks!Now it works! Thanks, Denico!
The reason I saved to text: The first time I followed your instructions, it did not work. I tried to figure out what I did wrong and saw that you wrote to "save as plain text." I did not know what this means and there was no option available to save a plain text. So I looked around and saw "save as stationery" and I guessed that maybe that was what you meant. And after that, it worked! But the next thing you know, the icons started duplicating themselves.
I guess I had made a different mistake in the beginning and I fixed it without knowing what it is.
Thanks for clearing that up.
But just one question. WHY does saving as "stationery" make an icon duplicate itself? -
Java Class (Compiled with JDK6_u12) that works with UCCX 9.0.2, don´t work with UCCX 10.5
I have a Java Class (Compiled with JDK6_u12) that works with UCCX 9.0.2, after upgrade it don´t work with UCCX 10.5
I get the error message: "Failed to access the WSDL at: https://www.brightnavigator.se/brightservice/brightservice.asmx?WSDL. It failed with: Got java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty while opening stream from https://www.brightnavigator.se/brightservice/brightservice.asmx?WSDL.; nested exception is: javax.xml.ws.WebServiceException: Failed to access the WSDL at: https://www.brightnavigator.se/brightservice/brightservice.asmx?WSDL. It failed with: Got java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty while opening stream from https://www.brightnavigator.se/brightservice/brightservice.asmx?WSDL. (line: 1, col: 47)
Does anyone know about this ?Did you ever find a resolution to this issue? I have a similar issue after upgrading from 7 to 10.5. I have loaded all provided certificates to the tomcat-trust store, restarted Tomcat Services and still get the same error
Thanks -
Are there other internet browsers that work well displaying websites with a lot of Flash content?
Other than the browser that came on the Samsung Droid Charge....
Are there other internet browsers that work well displaying websites with a lot of Flash content?
Thanks in advance!I use Dolphin Browser 6.0. Its faster than 5.0 and has no issues with Flash. I have used flash and used the Beta 6.0 and now the actual released version. Its the best so far. It has tabs like a normal computer browser and even has a gesture feature to do scrolling.
Others are Firefox which has NO flash. Then there is SkyFire which is ok, uses its servers to compress data and show it on your phone, its quick but I found the quality of images not as good as stock.
Opera Mobile and Mini do the same as skyfire.
I personally just didnt care for Xscope of Miren browsers. Didnt care for the feel of Xscope and Miren was developed in China and is modeled after Iphone Browser.
Try em all if you want, biggest benefit of the aftermarket browser is you can sync certain accounts (dolphin with google, firefox with firefox) and instead of storing the Cache info using phone memory you can now save the data and the web browser on the SD card. -
Can't execute web app from NetBeans 3.6 with Sun Java App Server 8
Hi there,
I'm tyring to execute a java web application called myfirstjsp.
In directory ...\myfirstsjp I've got:
- index.jsp
- WEB-INF dir
- META-INF dir.
I can run myfirstjsp from NetBeans if I choose the Netbeans default server, Tomcat 5.0.19 (this web server is configured to port 8084).
However, when I try to execute myfirstjsp from NetBeans with Sun Java System Application Server 8(configured to port 8080), it gives me an annoying message:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I checked port conflicts but none found.
The other two options don't give me a place to start (I don't know what to do with domain.xml)
I'm working with:
- Windows XP Pro
- J2SE 1.4.2_04 (installed in C:\Program Files\j2sdk1.4.2_04)
- Sun Java Application Server 8 (installed in C:\Program Files\Sun\AppServer)
- Netbeans 3.6 + Sun Java System Application Server Plugin (installed in C:\Program Files\NetBeans3.6).
My PC has the following environment variables:
PATH(in user MGoncalv)=C:\Program Files\Sun\AppServer\bin;,?ut
PATH(system variable)=C:\Program Files\j2sdk1.4.2_04\bin;D:\ProgramFiles\OraReportNT\bin;C:\OraHome92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Personal Communications\;C:\Program Files\IBM\Trace Facility\;%SystemRoot%\system32\nls;%SystemRoot%\system32\nls\ENGLISH
CLASSPATH(system variable)=.;C:\OraHome92\jdbc\lib\ojdbc14.jar
By looking at the Sun App Server log file, I discovered that the log outputs of
- Start Default Server (a link in the folder created by the installation of Sun App Server)
- and trying to execute myfirstjsp from NetBeans through Sun App Server
are very similar.
Below is a piece of server.log when I tried to execute myfirstjsp from NetBeans through Sun App Server. Please, pay attention to the EJBC error:
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-19T17:20:05.198+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-05-19T17:20:08.713+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-19T17:20:09.384+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-19T17:20:14.752+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-19T17:20:14.772+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-19T17:20:14.792+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-19T17:20:20.200+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-19T17:20:23.645+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-19T17:20:24.336+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-19T17:20:26.098+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-19T17:20:27.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-19T17:20:27.921+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-05-19T17:20:27.931+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-05-19T17:20:30.004+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-05-19T17:20:33.459+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are: |#]
[#|2004-05-19T17:20:33.479+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.stream.err|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.ejb.codegen.JavaCompilerException: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:139)
at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:60)
at com.sun.ejb.codegen.Compiler.compile(Compiler.java:57)
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:293)
... 45 more
|#]
[#|2004-05-19T17:20:33.739+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.739+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5187 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-05-19T17:20:33.759+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.789+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|Exception while deploying : Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
.|#]
[#|2004-05-19T17:20:33.799+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-05-19T17:20:33.879+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-19T17:20:34.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-19T17:20:35.111+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-19T17:20:35.121+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-19T17:20:35.161+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-05-19T17:20:35.181+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-19T17:20:35.412+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-19T17:20:37.945+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-19T17:20:38.456+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.556+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.847+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.887+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.987+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.007+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.558+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\Sun\AppServer\imq\bin].|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1084983639568|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-19T17:20:39.588+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-05-19T17:20:44.475+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[com.sun.enterprise.admin.event.ConfigChangeEvent -- server [1 Change(s), Id:1, ts:1084983644465]]|#]
[#|2004-05-19T17:20:44.545+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1046:A change notification was not handled sucessfully, the server will need a restart for the change to be effective.|#]
Is this EJB compilation error normal ? if not what does it mean ? Sun Java App Server installation isn't OK ?
I tried to look into the Sun App Server Troubleshooting, searched forums... but couldn't squeeze any valuable info from any of them.
If you have any sugestion regarding this problem, or you know some web site that addresses it please tell me !
Many thanks,
MiguelI seem to have the same problem, I cant run sun application server 8.1. The server is in c:\sun\appserver\, I am using netbeans 4.1. I recieve the same comment above:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I cant see any port conflict, the server is set to port 4848. I dont know about any configurations.
This is the Exception:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:45:43.930+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:45:43.940+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:45:43.940+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:45:43.950+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:45:43.960+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:53.507+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:47:53.517+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:47:57.533+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:47:57.543+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:47:57.543+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
[#|2005-11-02T11:49:01.705+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:49:01.715+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:49:05.681+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:49:06.432+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:50:38.915+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:50:38.925+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Dcom.sun.aas.jdwpOptions=transport=dt_socket,server=y,suspend=n,address=9009
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/ -
Problems with the article Building JSR 168-Compliant Portlets with Sun Java
i try to make my first portlet with the article Building JSR 168-Compliant Portlets with Sun Java Studio Enterprise
But when start the portlet simulator in the sun java studio i have an error. I did all that the article says. Please help me!!
Thanks and sorry for my english
Errors generated by provider instance - see log output
Error in provider method getContent(): com.sun.portal.providers.ProviderException: JSPProvider.processJSPFile(): jsp=HarnessPortletContent.jsp, java.lang.NullPointerException
Message: Locale string - es_ES
Message: Obtained client type - html.
Message: Got session property "filePath" = "null".
Message: Locale string - es_ES
Message: Got String property "contentPage" for channel "HarnessPortletChannel" = "HarnessPortletContent.jsp".
Message: Locale string - es_ES
Message: Obtained client type - html.
Message: Client path - null
Message: Obtained template path: C:\Documents and Settings\jbonardi\jstudio_6ee_user\ps\desktop\default\HarnessPortletChannel\HarnessPortletContent.jsp
Message: Set session property "javax.portlet.http_session_id" to object "BC7F955E23394EF2EA8772E8B60F1CC4".
Message: Got localized String property "title" for channel "HarnessPortletChannel" = "HarnessPortletProvider".
Message: Boolean property "isEditable" for channel "HarnessPortletChannel" does not exist.
Message: Got localized String property "description" for channel "HarnessPortletChannel" = "HarnessPortletProvider".
Message: String property "helpURL" for channel "HarnessPortletChannel" exists.
Message: Got String property "helpURL" for channel "HarnessPortletChannel" = "desktop/usedesk.htm".
Message: Locale string - es_ES
Message: Got String property "docroot" for channel "HarnessPortletChannel" = "/portalserver/docs/".
Message: Got String property "contentPage" for channel "HarnessPortletChannel" = "HarnessPortletContent.jsp".
Message: Boolean property "showExceptions" for channel "HarnessPortletChannel" does not exist.
Message: Locale string - es_ES
Message: Obtained client type - html.
Message: Client path - null
Message: Obtained template path: C:\Documents and Settings\jbonardi\jstudio_6ee_user\ps\desktop\default\HarnessPortletChannel\HarnessPortletContent.jsp
Message: Locale string - es_ES
Message: Obtained client type - html.
Message: Client path - null
Message: Obtained template most specific path: C:\Documents and Settings\jbonardi\jstudio_6ee_user\ps\desktop\default\HarnessPortletChannel\HarnessPortletContent.jsp
Message: Obtained client type - html.
Message: Got collection property "hasHelpByMimeType" for channel "portlet_GoogleSearchPortlet.
Message: Got localized String property "title" for channel "portlet_GoogleSearchPortlet" = "__Portlet__portlet.GoogleSearchPortlet".
Message: Boolean property "isEditable" for channel "portlet_GoogleSearchPortlet" exists.
Message: Got String property "entityIDPrefix" for channel "portlet_GoogleSearchPortlet" = "portlet|GoogleSearchPortlet".
Message: Got session property "javax.portlet.portletc.renderParams.portlet|GoogleSearchPortlet|portlet_GoogleSearchPortlet" = "null".
Message: Got session property "javax.portlet.portletc.portlet|GoogleSearchPortlet|portlet_GoogleSearchPortlet.isTarget" = "null".
Message: Set session property "javax.portlet.portletc.portlet|GoogleSearchPortlet|portlet_GoogleSearchPortlet.isTarget" to object "false".
Message: Obtained client type - html.
Message: Collection property "roleMap" for channel "portlet_GoogleSearchPortlet" does not exist.
Message: Collection property "userInfoMap" for channel "portlet_GoogleSearchPortlet" does not exist.
Message: Boolean property "showExceptions" for channel "HarnessPortletChannel" does not exist.
Error: Error in provider getContent()
<<<<<<<< Stack Backtrace:
com.sun.portal.providers.ProviderException: JSPProvider.processJSPFile(): jsp=HarnessPortletContent.jsp, java.lang.NullPointerException
at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:880)
at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:777)
at com.sun.portal.providers.jsp.JSPProvider.getContent(JSPProvider.java:546)
at com.sun.portal.harness.HarnessPortletProvider.getContent(Unknown Source)
at com.sun.portal.harness.ProviderHarness.createContent(Unknown Source)
at com.sun.portal.harness.ProviderHarness.initProvider(Unknown Source)
at com.sun.portal.harness.ProviderHarness.getHarness(Unknown Source)
at org.apache.jsp.desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp._jspService(desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp.java:73)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497)
at org.apache.jsp.PSSim$jsp._jspService(PSSim$jsp.java:84)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:226)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.java:148)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2349)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1040)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151)
at java.lang.Thread.run(Thread.java:534)
java.lang.NullPointerException
at com.sun.portal.harness.HarnessPortletProvider.doGetContent(Unknown Source)
at _jspsC_0003a._Documents_00020and_00020Settings._jbonardi._jstudio_6ee_user._ps._desktop._default._HarnessPortletChannel._HarnessPortletContent_jsp._jspService(_HarnessPortletContent_jsp.java:215)
at com.sun.portal.providers.jsp.jasper3.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sun.portal.providers.jsp.JspServletWrapper.service(JspServletWrapper.java:182)
at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:863)
at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:777)
at com.sun.portal.providers.jsp.JSPProvider.getContent(JSPProvider.java:546)
at com.sun.portal.harness.HarnessPortletProvider.getContent(Unknown Source)
at com.sun.portal.harness.ProviderHarness.createContent(Unknown Source)
at com.sun.portal.harness.ProviderHarness.initProvider(Unknown Source)
at com.sun.portal.harness.ProviderHarness.getHarness(Unknown Source)
at org.apache.jsp.desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp._jspService(desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp.java:73)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497)
at org.apache.jsp.PSSim$jsp._jspService(PSSim$jsp.java:84)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:226)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.java:148)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2349)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1040)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151)
at java.lang.Thread.run(Thread.java:534)
>>>>>>>>
Message: Got String property "width" for channel "HarnessPortletChannel" = "thick".You�ve got to unmount the portal server fs from your project, disable the portlet builder plugin (Tools->options->,,,PortletBuilder) then erase the ps folder inside your ide profile and then start the portlet builder module again. Try to simulate it again and it should work.
Regards,
Pablo. -
"Message Driven Bean" doesn't work with Sun App Server
Hello all,
i have a little bit problems, running a simple "Message Driven Bean" under the Sun App Server. The deployment of it works fine, but after starting the SUN App Server i get the following error message:
An error occurred during the message-driven beancontainer initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces.
Has anybody a workaround for this problem?
The queue seems to be correctly installed. A simple client programm from the Sun Tutorial (Consumer & Producer) works fine without any Errors or Exceptions.
I am a little bit confused, because the queue seems to work with the client programms but not with a MDB running on the SUN App Server.
Thanks for you help!
Greetings
ManuelHello Mr Manuel!
could you plz help me with the steps for creating a message driven bean using netbeans ver 5.0(with Sun Java� System Application Server Platform Edition 8.2 )
I just know how to work with Session beans & Entity Bean, and am try to learn to work on Message Driven Beans too. there are no proper tutorials where i can find steps for creating these..
I need the steps from the scratch.,like creating QueueConnection Factory & Destination etc..
It will be gr8 if you can help me with this at the earliest .
Thank you
Bye -
Debugger that works with WebLogic 5.1?
Are there any debuggers currently available that will work with WebLogic
5.1?
I assume that VisualCafe 4.0 (Expert Edition) will support local debugging,
but I'm also interested in remote debugging which the Expert edition does
not support.
If not, does anyone know when VisualCafe Enterprise Edition 4.0 will ship?
Thanks.
GregHi!
I have problem to get the co-client debug project to run. Do you have
the same problem?
-----Original Message-----
From: Terry Potter [mailto:[email protected]]
Posted At: måndag, augusti 07, 2000 23:18
Posted To: tools
Conversation: Debugger that works with WebLogic 5.1?
Subject: Re: Debugger that works with WebLogic 5.1?
I use the deistributed debugging that comes with Visual Cafe by Webgain
v4.0. It works fine.
"Jim Piersol" <[email protected]> wrote in message
news:3989ccec$[email protected]..
Get a real debugger. Try BugSeeker from http://www.karmira.com
Jim Piersol
Senior Software Engineer
Sun Certified Java Programmer
Strata Group, Inc.
[email protected]
"Greg Kim" <[email protected]> wrote in message
news:8ibuit$35e$[email protected].. -
Found x-platform remote debugger that works with WLSv4.5.1!!
[att1.html]
Hi!
I have problem to get the co-client debug project to run. Do you have
the same problem?
-----Original Message-----
From: Terry Potter [mailto:[email protected]]
Posted At: måndag, augusti 07, 2000 23:18
Posted To: tools
Conversation: Debugger that works with WebLogic 5.1?
Subject: Re: Debugger that works with WebLogic 5.1?
I use the deistributed debugging that comes with Visual Cafe by Webgain
v4.0. It works fine.
"Jim Piersol" <[email protected]> wrote in message
news:3989ccec$[email protected]..
Get a real debugger. Try BugSeeker from http://www.karmira.com
Jim Piersol
Senior Software Engineer
Sun Certified Java Programmer
Strata Group, Inc.
[email protected]
"Greg Kim" <[email protected]> wrote in message
news:8ibuit$35e$[email protected].. -
How to cooperate the current mail system with Sun Java Commnication Suite 5
Dear all and Shane,
Excuse me for bothering you again.
Due to time limited, I would like to know how to cooperate the current mail system with Sun Java Commnication Suite 5. I mean I would like to use current mail system (mailscanner + postfix + courier-IMAP + clamav + spamassassin + webmail) and use the outlook connector to connect to Sun Java COMMS 5 to share the calendar, contacts only.
Right now I have done the testing by using outlook, mac mail, thunderbird to share calendar,contacts via Sun Java COMMS 5 in Centos Linux 5.
My plan is as following
1. Sun Java Communication suites 5 server ( I called it comms5 ) will be in DMZ zone and will open the necessary ports in firewall.
2. I will create more than six sub domain name in Sun Delegate server and the necessary accounts within these domain names.
3. All messages will be transmitted via Postfix and clients will retrieve from Courier-IMAP
4. All Clients included other branch offices will use different mail clients to share their calendars, contacts via COMMS5 ( But how will COMMS handle the messages such like invitation ? )
Any suggestions will appreciate.
PS: Is it possible to classify the contacts in outlook address book ?
For example, when user click the receiver, it will show like as following
GLOBAL ADDRESS BOOK
--Director
--and so on
----CN.BRANCH OFFICE
-----------CN01 EMAIL ADDRESS
-----------CN02 EMAIL ADDRESS
-----------CN03 EMAIL ADDRESS
and so on
----JP.BRANCH OFFICE
-----------JP01 EMAIL ADDRESS
-----------JP02 EMAIL ADDRESS
-----------JP03 EMAIL ADDRESS
and so on
----TW.BRANCH OFFICE
and Due to the user account is located in CN.BRANCH OFFICE, it will extend the CN.BRANCH OFFICE contacts level.
Excuse me for bad English, hope you can understand it.
Best Regards,
BruceDogz wrote:
Due to time limited, I would like to know how to cooperate the current mail system with Sun Java Commnication Suite 5.
I mean I would like to use current mail system (mailscanner + postfix + courier-IMAP + clamav + spamassassin + webmail) and use the outlook connector to connect to Sun Java COMMS 5 to share the calendar, contacts only.Getting your current mail system to 'co-operate' in this way will require more time then simply migrating the accounts of users on the current mail system to the comm-suite-5 installation and making use of UWC for Webmail access and ClamAV/SpamAssassin integration within the messaging MTA.
Also the use of Outlook Connector with a non-Sun IMAP backend isn't supported, nor is the use of a non-Sun IMAP backend possible with UWC.
Right now I have done the testing by using outlook, mac mail, thunderbird to share calendar,contacts via Sun Java COMMS 5 in Centos Linux 5. Once again I should remind you that CentOS is not a supported platform for comm-suite-5
Regards,
Shane. -
Apache,IIS integration with Sun Java System Application Server
Hi,
Is any one know the way to connect Sun Appserver with IIS and Apace server.
Edited by: shiju707 on Oct 10, 2007 8:22 PMI'm also looking at the same solution of how to configure IIS as the front end for the Sun Java System Application Server 9.1. I went though the following document from Sun, but still unable to configure the IIS as the front end of the application server.
http://docs.sun.com/app/docs/doc/819-3679/abdhq?a=view
After i have configured the IIS, the ISAPI filter shown the status down for the Sun Load balancer plugin.
Did anyone have any idea of how can i configure IIS to working the Sun Java System Application Server 9.1? -
ColdFusion compatibility with Sun Java System Application Server
Background: A vendor that is doing a project for our
department told us that ColdFusion MX 6.1 is not compatible with
Sun Java System Application Server Enterprise Edition 8.1 and
beyond. Since we are migrating our server environment to this
release of Sun Java System Application Server Enterprise Edition,
we face a difficult situation in that our ColdFusion applications
will no longer run. Thus, we would like Adobe to answer a couple
questions which will help us determine what course of action we
ought to take.
Q: Will applications we developed using ColdFusion MX 6.1 run
on Sun Java System Application Server Enterprise Edition 8.1? Below
is a detailed description of the Sun Java System Application Server
Enterprise Edition we intend to migrate to.
Q: Is Adobe aware of any compatibility issues with this
configuration?
Q: What is Adobe's support commitment regarding future
releases of ColdFusion MX and Sun Java System Application Server
Enterprise Edition? Does Adobe intend to continue support this
environment?
Configuration: Sun Java System Application Server Enterprise
Edition 8.1_02 (build b24-p11)
Below is the specification levels for the 8.1 server
(J2EE1.4), note it can use J2SE 1.4.2_06 or 5.0 as the JAVA
runtime.
J2EE 1.4 compatible
Components: J2SE 1.4.2_06 or J2SE 5.0
Application and Application Client
Enterprise JavaBeans (EJB) 2.1
Java Servlet 2.4
JavaServer Pages(JSP) 2.0
J2EE Connector Architecture 1.5
JMX 1.2
JMS 1.1
Java Naming and Directory Interface (JNDI) 1.2
and Java Transaction API (JTA) 1.0
Web Services:Java Web Services Developer Pack 1.5
Java APIs for XML Registries (JAXR) 1.0
Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.1
SOAP With Attachments API for Java (SAAJ) 1.2
WS-I Basic Profile 1.0
Other:J2EE Deployment 1.1
J2EE Management 1.0
Java API for XML Processing (JAXP) 1.2
JavaMail 1.3
Java Authentication and Authorization Service (JAAS) 1.0
Java Authorization Contract for Containers (JACC) 1.0First of all, is there a reason why you are using jRockit?
Since the issue appeared after upgrading the windows, the issue would potentially be in the interaction between JVM and OS.
Also, there were some issues related to memory leak that were fixed in AS 8.2.
May be you should try with a Sun JVM and AS 8.2. -
Integrate p6SPY with Sun Java System Application Server 7 ...?
Dear PALs,
Let me know how can I Integrate p6SPY (w3.p6spy.com) with "Sun Java System Application Server 7 2004Q2" on Windows ?
When I try to follow the steps given at http://www.p6spy.com/documentation/install.htm#unspec ,my server throws
INFO ( 1820): JMS5035: Timed out after 30000 milliseconds while trying to verify if the JMS service startup succeeded.
INFO ( 1820): JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server1. Please refer to the JMS provider documentation for the exact location of this log file.
[27/Dec/2004:18:37:35] SEVERE ( 1820): JMS5024: JMS service startup failed.
[27/Dec/2004:18:37:35] SEVERE ( 1820): CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [NARAYANA:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:247)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:224)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [NARAYANA:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:231)
... 2 more
expecting sagacious reply......
thanks,
SIMPLEbnmHi,
You can set the p6SPY on Sun Java System Application Server as follows.
Create a connection pool using Admin Console, please don't specify any database vendor. Then use the following properties.
Data Source Class Name : com.p6spy.engine.spy.P6DataSource
Resource Type : javax.sql.DataSource
and then provide the following property.
user, password and url. Make sure you add the p6spy.jar and properties file to the classpath.
Try to ping the connection pool, and it should work. -
Problem with Sun Java Creator JDBC driver .....
Hi:
I am new to Java Studio Creator. I am using Oracle Enterprise Edition 8.0.5.0 database to get data from. Through Servers Navigator->Data Sources, I define a new datasource using default JSC JDBC driver for Oracle. However, when I try to test the connection I get the following error.
[sunm][Oracle JDBC Driver] Internal Error: Net8 Protocol Error
Can someone tell me what is going on here? By the way I also have Netbeans 4.0 IDE which works fine with the same database.
-Victor baggaI was using the following database URL.
jdbc:sun:oracle://autoserv.cqtel.com:1521;SID=autosvdb
The SID is valid because I can use other JDBC drivers such as Oracle's thin driver which uses the Database URL
jdbc:oracle:thin:@autoserv.cqtel.com:1521:autosvdb
and it works. However, I can not use the Oracle thin JDBC driver with Sun Java Creator as it seems to be incompatible. Using this driver I can successfully define a datasource and veiw all the data and make all kind of queries through the Server Navigator window but when I try to drop a database table on to a Data Table in my project, nothing happens. If I try to Edit the query on the rowset, the GUI window does not show any Column names and display names.
By the way, I also have an Oracle 9.x database which works just fine with Java Ctreator Studio. I really like Java Creator as I find it very productive but not being able to make it work with Oracle 8.0.5.0 takes the fun out of it. -
Please could you tell me what DLT/SDLT/Ultrium series drive works with Sun Fire V880 with SCSI Sun X
Please could you tell me what DLT/SDLT/Ultrium series drive works with Sun Fire V880 with SCSI Sun X6540A?
The question is URGENT because we need to do backup/restore of our Databases but we have not backup device...
We want to buy it but we don't know what exactly drives we can choose for our Sun with X6540A SCSI card.Hello,
the X6540A is a Dual Single-Ended Ultra/Wide SCSI (PCI) controller. The controller is only upto 40MB/sec, which might be suficient for a SDLT600 or LTO-2.
Every Single-Ended SCSI device works with this card, <b>but</b> performance would be low when using LVD/SE devices (some LVD devices can't operate in SE mode!)
I would suggest that you call Sun Sales.
I guess that the <b>PCI/PCI-X Dual Ultra320 SCSI Adapter</b> (SG-XPCI2SCSI-LM320) or <b>PCI Dual Ultra3 SCSI Host Adapter (LVD)</b> (X6758A) are a better choice if attaching more recent drives.
This is the <b> Sun Fire V880 - Full Components List</b>.
Michael
Maybe you are looking for
-
PDFs will not open in Browser with Adobe Reader 9
I am using Vista Ultimate x64 (SP1) using IE7. I am using the 32-bit version of the browser. I have selected "Display PDF in browser" on the Internet settings tab of the Adobe Reader 9. Every time I select a PDF document, it forces me to save the doc
-
The songs change really slow and it seems to actually freeze eerytime i change the song that is playing is there a way to fix that?
-
Bridge has never launched - Error code 6 on installation - So frustrated with "support" - HELP!
So, I'm going to rant just like everyone else here. It makes me feel better. I spent 11 HOURS on the phone with Adobe's foreign support team yesterday and still, nothing is resolved! At this point, I will not relent until my problem is solved. Here's
-
Hi. I need a source code that prints MS Word document across Java. I anyone has such code please send to my e-mail: [email protected] I am desperated.... Thank you. Charles
-
Hello, We need to change SLD layout from what is depicted on the left side on the picture below to the solution depicted on the right side. The reason for this is that services in SAP Landscape that depend on SLD are stopped during Solution Manager m