Exception when starting flex apache module

Hi all,
I'm trying to install the flex apache module on a server but
I get an exception when I start apache.
This are the info relating to my system:
[root@reilabs-www adobe]# uname -a
Linux server 2.6.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT
2007 i686 i686 i386 GNU/Linux
[root@server adobe]# java -version
java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode,
sharing)
[root@rserver adobe]# /opt/adobe/flex_sdk_3/bin/mxmlc
-version
Version 3.0.0 build 477
I get this when I start apache with: service httpd start:
[root@server]# Exception in thread "main"
java.lang.StringIndexOutOfBoundsException: String index out of
range: -1
at java.lang.String.substring(Unknown Source)
at flex2.tools.apache.RemoteApplication.initRequest(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native
Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown
Source)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown
Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown
Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at
flex2.tools.apache.RemoteApplication_Stub.initRequest(Unknown
Source)
at flex2.tools.apache.LocalApplication.compile(Unknown
Source)
at flex2.tools.apache.Client.main(Unknown Source)
I followed instruction and I installed the flex_sdk_3 in
/opt/adobe/flex_sdk_3, installed the flex apache module in the same
dir, then I edited the compiler.sh file setting the correct path to
the flex home dir, then I placed in /etc/httpd/conf/htttpd.conf
these lines:
LoadModule flex_module
/opt/adobe/flex_sdk_3/modules/apache/linux/22/mod_flex.so
AddHandler flex .mxml
Can you hint about a possible solution to this problem?
Many thanks in advance, best regards.

I am facing the same problem too... Do we have any solution to the problem while apache module for flex falis while it starts with the StringIndexOutofBoundsException ?

Similar Messages

Multicast Exception when starting a managed weblogic server.

I receive a Multicast Exception when i try to start a managed weblogic server from the same machine on which my admin server is running.
 when i try to start a managed server from another machine then it does not allow me to do so.
 please help,
 Manish.


see Sanjeev Chopra's response on 10/25/00 , subject named "
weblogic.admin.host -- missing
property"...
Kumar
John Kelvie wrote:
I am having the same problem...any suggestions?
"Srividhya" <[email protected]> wrote in message
news:3a107849$[email protected]..
Hi All,
While starting the weblogic managed server, i get the following error:
Starting WebLogic Server ....
<Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognizedproperty: ad
min.host>
<Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Errorconnect
ing to admin server and initializing admin home: admin URL:t3://kerala:7001
javax.naming.ServiceUnavailableException. Root exception isjava.rmi.NoSuchObje
ctException: The object identified by [3] could not because found. Eitherit was
has not been exported or it has been collected by the distributed garbagecolle
ctor.
atweblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
78)
atweblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
alContextFactoryDelegate.java:306)
atweblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:261)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:230)
at weblogic.jndi.Environment.getContext(Environment.java:129)
atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
atweblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
at weblogic.management.Admin.start(Admin.java:295)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
On the admin server, it does not give any error.
What could be the reason?
Regards,
Srividhya

Exception when starting WebToGo-Application

Hi,
when I start a WebToGo-Application on the Mobile Client, I get this Exception:
javax.servlet.ServletException: kta.replikation._Replikation.class not found
"Replikation" is the JSP which should be displayed when starting the application. The file exists in the our Mobile Server's repository. Can anyone tell me, why the application can't find this file?
Kind regards,
Simon

Hi Santharam,
I believe this is a side effect of two cluster members having different versions of the same class due concurrent development and testing. The best way to separate the clusters is to set each to use a different multicast address for the cluster communication. this can be done easily by using the following command line argument:
<tt>-Dtangosol.coherence.clusteraddress=224.1.1.x</tt>
Where 'x' is a value between 1 and 254.
I would also suggest setting the time-to-live of the multicast messages to zero so that the communication does not go beyond the development machine. This can be done with a similar command line argument:
<tt>-Dtangosol.coherence.ttl=0</tt>
Hope this helps.
Later,
Rob Misek
Tangosol, Inc.
Coherence: Cluster your Work. Work your Cluster.

Exception when starting emanager

Hi All,
When trying to go to the "deployer" page in the emanager I'm getting an error of a connect timeout.
During the startup of emanager (startserver.bat) I'm getting the following exception:
2008-02-26 22:37:16,218 INFO com.stc.egate.em.services.bridge51x.server.ma.ServerProxy [main] - HTTP service started with host: 192.168.2.17 port=15003
2008-02-26 22:37:16,218 ERROR com.stc.egate.em.services.bridge51x.server.ma.ServerProxy [main] - Unable to start HTTP Adaptor
java.net.BindException: Cannot assign requested address: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at mx4j.tools.adaptor.PlainAdaptorServerSocketFactory.createServerSocket(PlainAdaptorServerSocketFactory.java:24)
at com.stc.egate.em.services.bridge51x.server.connectors.StcHttpAdaptor.createServerSocket(StcHttpAdaptor.java:681)
at com.stc.egate.em.services.bridge51x.server.connectors.StcHttpAdaptor.start(StcHttpAdaptor.java:487)
at com.stc.egate.em.services.bridge51x.server.ma.ServerProxy.startHTTPService(ServerProxy.java:202)
at com.stc.egate.em.services.bridge51x.server.ma.ServerProxy.startServices(ServerProxy.java:484)
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:585)
at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at com.stc.egate.em.services.bridge51x.server.ma.ManagementAgent.start(ManagementAgent.java:147)
at com.stc.egate.em.services.bridge51x.ApplicationPathResolverListener51x.contextInitialized(ApplicationPathResolverListener51x.java:33)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3805)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4321)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:613)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:431)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:964)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:476)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2298)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)
java.net.BindException: Cannot assign requested address: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at mx4j.tools.adaptor.PlainAdaptorServerSocketFactory.createServerSocket(PlainAdaptorServerSocketFactory.java:24)
at com.stc.egate.em.services.bridge51x.server.connectors.StcHttpAdaptor.createServerSocket(StcHttpAdaptor.java:681)
at com.stc.egate.em.services.bridge51x.server.connectors.StcHttpAdaptor.start(StcHttpAdaptor.java:487)
at com.stc.egate.em.services.bridge51x.server.ma.ServerProxy.startHTTPService(ServerProxy.java:202)
at com.stc.egate.em.services.bridge51x.server.ma.ServerProxy.startServices(ServerProxy.java:484)
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:585)
at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at com.stc.egate.em.services.bridge51x.server.ma.ManagementAgent.start(ManagementAgent.java:147)
at com.stc.egate.em.services.bridge51x.ApplicationPathResolverListener51x.contextInitialized(ApplicationPathResolverListener51x.java:33)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3805)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4321)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:613)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:431)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:964)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:476)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2298)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)
2008-02-26 22:37:17,359 INFO com.stc.egate.em.services.bridge51x.server.ma.ServerProxy [main] - Timer service started.
java.io.IOException: Cannot bind to URL [rmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.
Any ideas what could be the problem?
Thanks.

Thanks for the reply.
I wasn't able to find anything using that port.
Anyway I re-installed the eManager and now it start fine (still using the same port so it doesn't look like that was the problem).
I think that the problem has something to do with the ip address it was trying to use (192.168.2.17), that address doesn't exist in my network. After the re-installation it is no longer trying to use that address but my machine name.
Does the eManager record the ip address or the machine name during the installation process? Is it configurable? I couldn't find any such configuration.

Exception when starting sun studio

when am starting sun studio, it is giving an error message (exception)-java.lang.out of memory error : java heap space.
i cant able to start sun studio. What will do...?
Thanks in advance
vinod

Check current limits by issuing; this output is from my Ubuntu machine:
$ ulimit -a
core file size (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16379
max locked memory (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size              (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 16379
virtual memory          (kbytes, -v) unlimited
file locks (-x) unlimited
I marked settings that would probably need closer attention. Easies way to troubleshoot the problem is to set everything to unlimited and see if it helps.
Also, check if you have enough swap - Sun Studio needs at least one gig of swap and 512 RAM (see http://docs.sun.com/source/820-2973/release_notesML.html#SystemReqs).

Exception when starting jboss

when i starting jboss i am getting following exceptions hot to solve it
java.net.BindException: Address already in use: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
 at java.net.ServerSocket.bind(ServerSocket.java:309)
 at java.net.ServerSocket.<init>(ServerSocket.java:183)
 at org.jboss.web.WebServer.start(WebServer.java:160)
 at org.jboss.web.WebService.startService(WebService.java:104)
 at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
 at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:398)
 at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
 at $Proxy3.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:569)
 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.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:536)
10:24:49,703 WARN [ServiceController] Problem starting service jboss:service=Webserver
java.net.BindException: Address already in use: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
 at java.net.ServerSocket.bind(ServerSocket.java:309)
 at java.net.ServerSocket.<init>(ServerSocket.java:183)
 at org.jboss.web.WebServer.start(WebServer.java:160)
 at org.jboss.web.WebService.startService(WebService.java:104)
 at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
 at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:398)
 at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
 at $Proxy3.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:569)
 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.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:536)
java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
 java.net.BindException: Address already in use: JVM_Bind
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
 at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
 at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
 at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:129)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:275)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:206)
 at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:422)
 at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:263)
 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.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:398)
 at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
 at $Proxy3.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:569)
 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.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:536)
Caused by: java.net.BindException: Address already in use: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
 at java.net.ServerSocket.bind(ServerSocket.java:309)
 at java.net.ServerSocket.<init>(ServerSocket.java:183)
 at java.net.ServerSocket.<init>(ServerSocket.java:95)
 at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
 at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
 at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
 ... 41 more
10:24:50,359 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp
java.rmi.ServerException: Could not bind JRMP invoker; nested exception is:
 java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
 java.net.BindException: Address already in use: JVM_Bind
 at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:284)
 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.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:398)
 at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
 at $Proxy3.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:569)
 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.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:536)
Caused by: java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
 java.net.BindException: Address already in use: JVM_Bind
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
 at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
 at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
 at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
 at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:129)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:275)
 at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:206)
 at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:422)
 at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:263)
 ... 32 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
 at java.net.ServerSocket.bind(ServerSocket.java:309)
 at java.net.ServerSocket.<init>(ServerSocket.java:183)
 at java.net.ServerSocket.<init>(ServerSocket.java:95)
 at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
 at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
 at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
 at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
how to solve it
plz help me
thanks in advance

Has anyone solved this issue as I am getting it too
thanks
16:35:31,078 INFO [Server] Starting JBoss (MX MicroKernel)...
16:35:31,078 INFO [Server] Release ID: JBoss [WonderLand] 3.2.3 (build: CVSTag=
JBoss_3_2_3 date=200311301445)
16:35:31,078 INFO [Server] Home Dir: C:\jboss-3.2.3
16:35:31,078 INFO [Server] Home URL: file:/C:/jboss-3.2.3/
16:35:31,078 INFO [Server] Library URL: file:/C:/jboss-3.2.3/lib/
16:35:31,078 INFO [Server] Patch URL: null
16:35:31,078 INFO [Server] Server Name: default
16:35:31,078 INFO [Server] Server Home Dir: C:\jboss-3.2.3\server\default
16:35:31,078 INFO [Server] Server Home URL: file:/C:/jboss-3.2.3/server/default
16:35:31,093 INFO [Server] Server Data Dir: C:\jboss-3.2.3\server\default\data
16:35:31,093 INFO [Server] Server Temp Dir: C:\jboss-3.2.3\server\default\tmp
16:35:31,093 INFO [Server] Server Config URL: file:/C:/jboss-3.2.3/server/defau
lt/conf/
16:35:31,109 INFO [Server] Server Library URL: file:/C:/jboss-3.2.3/server/defa
ult/lib/
16:35:31,125 INFO [Server] Root Deployment Filename: jboss-service.xml
16:35:31,125 INFO [Server] Starting General Purpose Architecture (GPA)...
16:35:31,359 INFO [ServerInfo] Java version: 1.4.2_03,Sun Microsystems Inc.
16:35:31,359 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_03-b02
,Sun Microsystems Inc.
16:35:31,375 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
16:35:31,421 INFO [ServiceController] Controller MBean online
16:35:31,515 INFO [MainDeployer] Started jboss.system:service=MainDeployer
16:35:31,593 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeplo
yer@8bdcd2
16:35:31,593 INFO [JARDeployer] Started jboss.system:service=JARDeployer
16:35:31,625 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeplo
yer@12d263f
16:35:31,640 INFO [SARDeployer] Started jboss.system:service=ServiceDeployer
16:35:31,640 INFO [Server] Core system initialized
16:35:31,656 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.3/server/default/conf/jboss-service.xml
16:35:33,625 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
16:35:33,890 INFO [LocalJBossServerDomain] Started jboss.management.local:j2eeT
ype=J2EEDomain,name=Manager
16:35:33,906 INFO [Log4jService] Started jboss.system:type=Log4jService,service
=Logging
16:35:33,921 INFO [WebService] Started WebServer with address: 0.0.0.0:8083
16:35:33,921 INFO [AbstractDeploymentScanner$ScannerThread] Running
16:35:33,937 INFO [WebService] Using RMI server codebase: http://rel-serv1:8083
16:35:33,937 INFO [WebService] Started jboss:service=WebService
16:35:33,953 INFO [NamingService] Starting jnp server
16:35:34,031 INFO [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=5
0, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jbo
ss.net.sockets.DefaultSocketFactory@ad093076
16:35:34,062 INFO [NamingService] Listening on port 1099
16:35:34,078 INFO [NamingService] Started jboss:service=Naming
16:35:34,078 INFO [JNDIView] Started jboss:service=JNDIView
16:35:34,078 INFO [SecurityConfig] Started jboss.security:service=SecurityConfi
g
16:35:34,125 INFO [XMLLoginConfig] Started jboss.security:service=XMLLoginConfi
g
16:35:34,140 INFO [JaasSecurityManagerService] Started jboss.security:service=J
aasSecurityManager
16:35:34,187 INFO [TransactionManagerService] Started jboss:service=Transaction
Manager
16:35:34,218 ERROR [JRMPInvoker] Starting failed
java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:14
5)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:12
9)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.
java:275)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.
java:206)
at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.jav
a:394)
at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker
.java:305)
at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvok
er.java:108)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
92)
at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:5
66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)

Strange unmarshalling exception when starting RMI server

I've run into a strange problem when running my RMI server. It worked fine yesterday, though I made a few changes since then, none of those changes should cause this to happen, as far as I know.
Here's the exception:
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: pub.interfaces.ClientIface
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
at java.rmi.Naming.rebind(Naming.java:160)
at priv.server.TCMaster.<init>(TCMaster.java:97)
at priv.server.TCMaster.main(TCMaster.java:71)
Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: pub.interfaces.ClientIface
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException: pub.interfaces.ClientIface
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at sun.rmi.server.LoaderHandler.loadProxyInterfaces(LoaderHandler.java:707)
at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:651)
at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:588)
at java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoader.java:628)
at java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.java:294)
at sun.rmi.server.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:238)
at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1494)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1457)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
... 9 more
pub.interfaces.ClientIface is in the SAME directory as the RMI server class! What could be causing this?
NOTE: I'm running this on Redhat Linux 9, jdk 1.5.0_04.

Usually an unmarshalling exception is caused by the classes not matching up on the server & client end. The classes are there I think, because otherwise it would have thrown a classnotfound exception instead. Can you try actually copying and pasting the classes either from the server to the client or vice versa? I've had weird issues where sometimes the compiler compiles the same class differently in different locations, so your safest bet is to make sure the client & server classes (that you're passing as arguments & returning from the server) are identical.
Good luck!

Getting Win32 exception when starting Oracle Infrastructure iasconsole

Installed Oracle Infrastructure server 10GR1 and everything appears to be working EXCEPT I keep getting these "Visual Stidio Just-In-Time Debugger" pop-ups saying "An unhandled WIN32 exception occurred in nmupm.exe and also cmd.exe"
Any ideas?
Stumped in Boston

I have found out the problem and solution for this OPMN error, its actually our Fusion team work
the error is caused by Port conflicts we believe
so by using these set of commands of opmnctl
usage: opmnctl [verbose] [<scope>] <command> [<options>]
verbose: print detailed execution message if available
Permitted <scope>/<command>/<options> combinations are:
scope command options
start - Start opmn
startall - Start opmn & all managed processe
stopall - Stop opmn & all managed processe
shutdown - Shutdown opmn & all managed proce
[<scope>] startproc [<attr>=<val> ..] - Start opmn managed processes
[<scope>] restartproc [<attr>=<val> ..] - Restart opmn managed processes
[<scope>] stopproc [<attr>=<val> ..] - Stop opmn managed processes
[<scope>] reload - Trigger opmn to reread opmn.xml
[<scope>] status [<options>] - Get managed process status
[<scope>] dmsdump [<attr>=<val>&..] - Get DMS stats
[<scope>] set [<attr>=<val> ..] - Set opmn log parameters
[<scope>] query [<attr>=<val>] - Query opmn log parameters
ping [<max_retry>] - Ping local opmn
validate [<filename>] - Validate the given xml file
config [<options>] - Modify the opmn xml file
help - Print brief usage description
usage [<command>] - Print detailed usage description
we have shutdown the opmn box and restarted all of its process
it did not happen in the first time itself i have to repeat this for a several times then the SOA suite is running normally
if any one faces this issue i can help

Exception when starting CachePreloaderService

Dear Portal Specialists
We upgraded our portal to NW 7.0 EHP1 SPS 3 and want to enable Navigation Cache and the CachePreloaderService.
So first i enabled the Navigation Cache and then i configured the CachePreloaderService.
Run on startup: true
Users to preload: [Administrator:2:false:en_US,en] (i also tried custom values)
When i go to the node to restart the service, i receive the following error:
Server 1991650:Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of handleTopic.
I can find other threads about the same error message, but those are about custom services or services that had to be deployed.
Does anybody know this problem and knows how to solve it?
Thank you very much and best regards
Martin

Dear Sandra
thank you very much for the detailled infos!
Following some responses and some more questions:
We set the FPN Cache validity to 43'200 = 12 h
We think about changing that. But this will have influence on our transport process for our BI systems, so we first have to think about it.
The navigation is not slow on every click. We also assume that it is only slow when cache expired. But since we have 8 server nodes, this behavior is not that easy to really verify.
Usually only the loading of the first opening of the detail navigation is slow, but opening the subfolders is not slow.
However, from time to time it is also slow to open subfolders.
I don't understand the functionality of the synchronize button exactly.
It seems that it loads the current info from the systems and caches it. (the message after it is finished sais that the cache got renewed.)
So my conclusion is, that if the system gets restarted, and we click this button, we don't have to expect bad performance. Is this correct?
You write about opening all the navigation structure after cache expired, is this necessary? How are you doing this (did you find a way for automation?)
We did a test, of the synchronizing, but we have to do more tests.
Do you recommend to load all content or only the changed content (first radio button option to chose from)
We did not configure the OptimizerC service.
According to SAP help it is only used for RRA but not for RDL. So this does not help in our case.
We also connected BI Systems with FPN (except from one iview from CE)
We also have problem with the synchronization from time to time, so RDL is not the perfect solution.
Can you tell me, if you have 32 of 64bit servers?
I got a recommendation from SAP to set the Pcd.Xfs.Cache.HardReferenceLimit to 500 instead of 100 (Note 905211)
But we have only 32bit servers (will be replaced one day) so we have some concerns to set 500. Do you have any experience with this setting?
Thank you very much and best Regards
Martin

Null pointer exception when starting application

Hi:
I had a application running fine, then i had to change some parameters in my RFC. I reimported the model, removed all the excess mapping, rebuild, deployed , restarted the server.
Then when i run the application, i get the below error.
Anyone has any idea?
java.lang.NullPointerException
 at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initReferenceAttribute(AttributeInfo.java:503)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initStructureType(NodeInfo.java:808)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:757)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
 at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initAttributeMapping(AttributeInfo.java:596)
 at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:456)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:373)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Hi Subramania,
You said:
"I had a application running fine, then i had to change some parameters in my RFC. I reimported the model, removed all the excess mapping, rebuild, deployed , restarted the server."
You have removed all mappings between controller and view.
But, have you removed bindings between context attributes and view elements?
I guess problem is in binding between context and ui elements only.
Check it out and let me know.
Regards,
Bhavik

Unhandled exception when starting headstart utilities 6i

Installed Designer 6i (4.1.1), Developer patch 7, Headstart 6.5.
Try to launch Headstart utilities, logon, get the context workarea question. Choose the only one we've got, and get error message:
Unhandled exception in SET_CONTEXT_WORKAREA:ORA-4020:deadlock detected while trying to lock object HSU65.BLAPI, trg block: WKA, trg item:WKA.
CONTEXT_WORKAREA_IRID
Anyone any ideas?
Thanks!

Ernst,
Did you recently upgrade your Oracle Designer version?
You probably have to re-run the grants script, that grants access on Repository objects to the Utilities owner.
To do this, log on to SQL*Plus as the Oracle Repository Owner, and run the following script, located
in the [Headstart Home]\hsu\scripts directory, with the following command line parameters.
d6grtsyn.sql [Headstart Home] [Utilities Owner schema name]
for example:
d6grtsyn.sql c:\hsd65 hsua65
SQL*Plus will be closed automatically. The log file d6grtsyn.log will be created in the Headstart Home.
Check this log file for any errors.
kind regards,
Sandra

Exception when start Adobe Interactive form (Webdynpro)

Hello everyone,
I am trying to launch Webdynpro application (from NWDS) with Adobe form. And get error message:
javax.xml.rpc.soap.SOAPFaultException: javax.ejb.EJBAccessException: Principal: Guest (authentication method: unknown), policyContextID: com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar, permission.name: AdobeDocumentServicesEJB, permission.actions: rpData,Remote,com.adobe.RpString[],com.adobe.RpStream[].
p.s. I have added ADSUser to Administrators group.
Appreciate any help!
Kirill

Hello Arafat,
What I have done:
1. Got credential files from
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10e507e7-2670-2a10-0ba5-eaaabdf7c221
0004793_Exp09302008.pfx
0004793_Exp09302008.txt (password) file
2. Moved 0004793_Exp09302008.pfx to the
C:usrsapCE1SYSglobalAdobeDocumentServicesTrustManagerService rustcredentials
3. Created two attributes:
a. ReaderRights (without sha-1)
b. DocumentCertification (without sha-1)
Assigned password from 0004793_Exp09302008.txt
Type: P12
P12 File: 0004793_Exp09302008.pfx.
4. Restared WAS.
Any ideas?
Regards,
Kirill

Exception in starting managed server

I am using WLS6.0 and have the exception when starting a newly created managed server.
The admin server console prompted the attached exception messages. It seems compliant
about security?
If someone know what's wrong, please share with me.
Thanks in advance!
<Feb 8, 2001 12:01:21 PM CST> <Critical> <Log Management> <Unable to contact managed
server - unitTest, at 202.45.228.90:8003. Domain logfile will not contain m
essages from this server.
java.lang.IllegalArgumentException: Invalid user name or password
at weblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.java:281)
at weblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHandler.java:243)
at weblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.java:183)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:559)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:545)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBeanServerImpl_WLSkel.java:382)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:103)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>

Yes, I started both admin and managed server with 'system' user with password typed
in password.ini file.
I used the default NT script startWeblogic.cmd and startManagedWeblogic.cmd to start
them.
Command prompt 1: startWeblogic.cmd
Command prompt 2: startManagedWeblogic.cmd newServer http://localhost:7001
The exception message goes to admin server's console while no error message goes
to the managed server's console.
"Sanjeev Chopra" <[email protected]> wrote:
Are you starting both managed and admin server with as the 'system' user
Is the system password password provided to both servers same ?
Please post your startup commands for both the servers.
kf cheung <[email protected]> wrote in message
news:[email protected]...
I am using WLS6.0 and have the exception when starting a newly createdmanaged server.
The admin server console prompted the attached exception messages. Itseems compliant
about security?
If someone know what's wrong, please share with me.
Thanks in advance!
<Feb 8, 2001 12:01:21 PM CST> <Critical> <Log Management> <Unable tocontact managed
server - unitTest, at 202.45.228.90:8003. Domain logfile will not containm
essages from this server.
java.lang.IllegalArgumentException: Invalid user name or password
atweblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.j
ava:281)
atweblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHand
ler.java:243)
atweblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.j
ava:183)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:559)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
45)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBean
ServerImpl_WLSkel.java:382)
atweblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
atweblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
atweblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
java:103)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
7)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>

Commons-logging Error when starting JRun with Flex

Created new JRun Server and deployed Flex2 to this server.
Receiving this error when starting up this server instance.
Starting Macromedia JRun 4.0 (Build 92909), logicerm2 server
07/13 22:23:28 info JRun Naming Service listening on *:2911
07/13 22:23:28 warning No sessionSecret has been specified in
jrun.xml. Installi
ng a self generated sessionSecret.
07/13 22:23:28 info No JDBC data sources have been configured
for this server (s
ee jrun-resources.xml)
07/13 22:23:28 info JRun Web Server listening on *:8102
07/13 22:23:28 info Deploying enterprise application
"default-ear" from: file:/C
:/JRun4/servers/logicerm2/default-ear/
07/13 22:23:28 info Deploying web application "JRun Default
Web Application" fro
m: file:/C:/JRun4/servers/logicerm2/default-ear/
07/13 22:23:29 info Web Services in default-ear#default-war:
07/13 22:23:29 info AdminService
07/13 22:23:29 warning default-war web application has
'reload' as true in jrun-
web.xml. Consider setting it false if the application is
running in production e
nvironment.
07/13 22:23:29 warning default-war web application has
'compile' as true in jrun
-web.xml. Consider setting it false if the application is
running in production
environment.
07/13 22:23:29 user JSPServlet: init
07/13 22:23:29 info Deploying web application "Flex Data
Services" from: file:/C
:/JRun4/servers/logicerm2/flex/
07/13 22:23:29 user JSPServlet: init
07/13 22:23:29 user FlexMxmlServlet: init
07/13 22:23:29 INFO Loading configuration file
C:\JRun4\servers\logicerm2\flex\W
EB-INF\flex\flex-webtier-config.xml
07/13 22:23:30 INFO Loading configuration file
C:\JRun4\servers\logicerm2\flex\W
EB-INF\flex\flex-config.xml
07/13 22:23:30 user FlexMxmlServlet: Starting Adobe Flex Web
Tier Compiler
07/13 22:23:30 user FlexMxmlServlet: Adobe Flex Web Tier
Compiler Build: 143451
07/13 22:23:30 user MessageBrokerServlet: init
07/13 22:23:31 user FlexSwfServlet: init
07/13 22:23:31 user FlexInternalServlet: init
07/13 22:23:31 info Deploying web application "Flex Admin Web
Application" from:
file:/C:/JRun4/servers/logicerm2/flex-admin/
07/13 22:23:31 user JSPServlet: init
07/13 22:23:31 user MessageBrokerServlet: init
07/13 22:23:31 info Deploying web application "Flex Data
Services Samples" from:
file:/C:/JRun4/servers/logicerm2/samples/
07/13 22:23:31 user JSPServlet: init
07/13 22:23:31 user FlexMxmlServlet: init
07/13 22:23:32 INFO Loading configuration file
C:\JRun4\servers\logicerm2\sample
s\WEB-INF\flex\flex-webtier-config.xml
07/13 22:23:32 INFO Loading configuration file
C:\JRun4\servers\logicerm2\sample
s\WEB-INF\flex\flex-config.xml
07/13 22:23:32 user FlexMxmlServlet: Starting Adobe Flex Web
Tier Compiler
07/13 22:23:32 user FlexMxmlServlet: Adobe Flex Web Tier
Compiler Build: 143451
07/13 22:23:32 user MessageBrokerServlet: init
07/13 22:23:32 error Could not pre-load servlet:
MessageBrokerServlet
[1]org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logg
ing.LogConfigurationException:
org.apache.commons.logging.LogConfigurationExcept
ion: Invalid class loader hierarchy. You have more than one
version of 'org.apa
che.commons.logging.Log' visible, which is not allowed.
(Caused by org.apache.co
mmons.logging.LogConfigurationException: Invalid class loader
hierarchy. You ha
ve more than one version of 'org.apache.commons.logging.Log'
visible, which is n
ot allowed.) (Caused by
org.apache.commons.logging.LogConfigurationException: or
g.apache.commons.logging.LogConfigurationException: Invalid
class loader hierarc
hy. You have more than one version of
'org.apache.commons.logging.Log' visible,
which is not allowed. (Caused by
org.apache.commons.logging.LogConfigurationExc
eption: Invalid class loader hierarchy. You have more than
one version of 'org.
apache.commons.logging.Log' visible, which is not allowed.))
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:543)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:235)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:209)
at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at
org.apache.commons.httpclient.params.DefaultHttpParams.<clinit>(Defau
ltHttpParams.java:53)
at
flex.messaging.services.http.HTTPProxyAdapter.<init>(HTTPProxyAdapter
.java:111)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Sou
rce)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
flex.messaging.util.ClassUtil.createDefaultInstance(ClassUtil.java:71
at
flex.messaging.Destination.createAdapter(Destination.java:277)
at
flex.messaging.Destination.initDestination(Destination.java:103)
at
flex.messaging.services.HTTPProxyService.createDestination(HTTPProxyS
ervice.java:78)
at
flex.messaging.services.AbstractService.createDestinations(AbstractSe
rvice.java:82)
at
flex.messaging.config.MessagingConfiguration.createServices(Messaging
Configuration.java:187)
at
flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
gConfiguration.java:84)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
5)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
java:1242)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
ice.java:789)
at
jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
va:291)
at
jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
ce.java:242)
at
jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
ce.java:179)
at
jrun.deployment.DeployerService.run(DeployerService.java:891)
at
jrunx.scheduler.SchedulerService.invokeRunnable(SchedulerService.java
:223)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
Caused by:
org.apache.commons.logging.LogConfigurationException:
org.apache.comm
ons.logging.LogConfigurationException: Invalid class loader
hierarchy. You have
more than one version of 'org.apache.commons.logging.Log'
visible, which is not
allowed. (Caused by
org.apache.commons.logging.LogConfigurationException: Inval
id class loader hierarchy. You have more than one version of
'org.apache.common
s.logging.Log' visible, which is not allowed.)
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:397)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:529)
... 30 more
Caused by:
org.apache.commons.logging.LogConfigurationException: Invalid class
l
oader hierarchy. You have more than one version of
'org.apache.commons.logging.
Log' visible, which is not allowed.
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:385)
... 31 more
[0]flex.messaging.config.ConfigurationException: Unable to
create service 'flex.
messaging.services.HTTPProxyService' for 'proxy-service' due
to the following er
ror: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.lo
gging.LogConfigurationException: Invalid class loader
hierarchy. You have more
than one version of 'org.apache.commons.logging.Log' visible,
which is not allow
ed. (Caused by
org.apache.commons.logging.LogConfigurationException: Invalid cla
ss loader hierarchy. You have more than one version of
'org.apache.commons.logg
ing.Log' visible, which is not allowed.) (Caused by
org.apache.commons.logging.L
ogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
Invalid class loader hierarchy. You have more than one
version of 'org.apache.c
ommons.logging.Log' visible, which is not allowed. (Caused by
org.apache.commons
.logging.LogConfigurationException: Invalid class loader
hierarchy. You have mo
re than one version of 'org.apache.commons.logging.Log'
visible, which is not al
lowed.)).
at
flex.messaging.config.MessagingConfiguration.createServices(Messaging
Configuration.java:202)
at
flex.messaging.config.MessagingConfiguration.configureBroker(Messagin
gConfiguration.java:84)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:10
5)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.
java:1242)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationServ
ice.java:789)
at
jrun.servlet.WebApplicationService.postStart(WebApplicationService.ja
va:291)
at
jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerServi
ce.java:242)
at
jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at
jrun.deployment.DeployerService.checkWatchedDirectories(DeployerServi
ce.java:179)
at
jrun.deployment.DeployerService.run(DeployerService.java:891)
at jrunx.scheduler.SchedulerS07/13 22:23:33 user
FlexSwfServlet: init
ervice.invokeRunnable(SchedulerService.java:223)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:426)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
PLEASE Help!!!
Bernie

This can happen if you have the default-ear that JRun creates
and you install the /samples files for Flex Data Services installed
together.
The problem is with the commons-logging.jar. If you copy the
commons-logging.properties file from the
samples\WEB-INF\flex\jars\commons-logging.properties directory to
the samples\WEB-INF\classes\commons-logging.properties directory,
it will resolve the problem.
This is listed as Adobe FDS bug: 179227

Error when starting Netscape Calendar Server: Module: , Label: 355, Service error: #0x13209

When starting Netscape Calendar Server, the following error message appears:
 
Module: , Label: 355, Service error: #0x13209

The three ACIs listed below need to be present in the Directory Server in order
for Calendar server to work properly. Check the properties on the Base DN to
verify that the following ACIs exist. If they are not present, you will need
to add them, and the Base DN will need to be modified for your enviroment.

<OL>
<LI>ACI for allowing users to modify their own entries. 

(targetattr = "*")(version 3.0; acl "Allow self entry modification";
allow (write)userdn = "ldap:///self";) 

<LI>ACI for allowing anyone permissions to Read, Search, and Compare. 

(target="ldap:///o=basedn.com") (targetattr != "userPassword") (version
3.0; acl "Anonymous access";
allow (read, search, compare) userdn = "ldap:///anyone";) 

<LI>ACI for allowing Calendar Server admins Write access to the Base DN
(this is necessary in order for admins to add users and resources to the node).
 
(target="ldap:///o=basedn.com") (targetattr = "*") (version 3.0; acl
"Calendar Administrators Group"; 
allow(all) groupdn = "ldap:///cn=Calendar Server Admins,ou=Netscape
Servers,o=basedn.com";) 
</OL>

Hi Trinidad,
Thanks for your help!!!
1.
I didn't install EventSender and DIProxy yet, I tried first to upload and deploy the zip files, but I couldn't open the Itegration Application Explorer.
2.
The jvm.dll file is in in the folder pointed by the logs: C:\Program Files (x86)\SAP\SAP Business One Integration\jdk1.5.0_xx_sap\jre\bin\server
and it is also in C:\Program Files (x86)\SAP\SAP Business One Integration\jdk1.5.0_xx_sap_64\jre\bin\server
I tried running the file java5w.exe, but I got an error message:
Access is denied
Unable to open the service tomcat5
Thne I managed to open it by "rua as administrator".
the Java Virtual Machine path is points to the java 1.5 version folder.
Is it possible that the reason that the service can't start is related to administrator rigts??
In the properties in the Integration Service (services.msc):
It is set to be run with the local system account.
all other properties looks fine.
in the properties of the tomcat5.exe (and tomcat5w.exe , I tried both)
In the Compatibility tab I tried setting the flag "Run this program in compatibility mode for" to Vista, windows 7, and server 2008
I didn't have the option of Windows XP.
I have also set the Privilege level of: "Run this program as administrator" to true.
But still the service won't start.
What can be the problem?
What else can I check?
Thanks a lot,
Chana

Exception when starting flex apache module

Similar Messages

Maybe you are looking for