Passing arguments to Managed Server ServerStart when using Node Manager

Below is the procedure to pass arguments to Managed Server serverstart tab when using Node Manager to start and stop the Managed Server instance
For passing the JVM arguments we will have to use "-server" which is hotspot and then pass the arguments
for eg: "-server -Xms2048m -Xmx2048m -verbosegc"
For adding jar's to the classpath you will have to add weblogic.jar and weblogic_sp.jar from WL_HOME/server/lib directory as well along with the custom jar (In some cases we can ignore weblogic_sp.jar, just adding weblogic.jar will do).
for eg: "\home\user\debug.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic_sp.jar;"
- - Tarun

Hi,
To me, if you don't wanna use the NodeManager, you won't be able to start your managed servers with WLST.
I guess the only ways are :
* through the console / WLST using the NodeManager
* using the startManagedWebLogic.[cmd/sh]
Regards

Similar Messages

Path problem when use node manager to start Managed Server

Hi, I have met a problem:
My managed server's root directory is /usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is /usr/local/bea/cluster1/weblogic700/common/nodemanager
I have some config file located under managed server's root directory and log
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server, I found
weblogic can not find the config file if I don't move the config file from Managed
server's root directory to node manager server's default directory. and also log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to node manager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Hi Lumin,
If the weblogic version is 8.1, there is a RootDirectory field in Remote
Start tab which should resolve your problem. Just enter the absolute
directory pathname on the machine where you are starting your managed server
and the current working directory of the managed server will be this
RootDirectory. Before 8.1, the RootDirectory was used for finding the config
file for weblogic but it was never used to change the working directory of
the managed server created by the node manager.
cheers,
gaurav.
"lumin" <[email protected]> wrote in message
news:3eb7a4ae$[email protected]..
>
Hi, I have met a problem:
My managed server's root directory is/usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is/usr/local/bea/cluster1/weblogic700/common/nodemanager
>
I have some config file located under managed server's root directory andlog
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server,I found
weblogic can not find the config file if I don't move the config file fromManaged
server's root directory to node manager server's default directory. andalso log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to nodemanager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Native IO Disabled when using node manager to start managed server

Hi,
I am able to start my node manager and the managed server from the Admin Console. OS is AIX, WebLogic 9.2 MP3. The managed server starts OK, but Native IO is disabled even though it is enabled in the Admin Console for that manager server:
####<Jul 28, 2009 8:25:00 AM CDT> <Info> <Socket> <pstps09.statefarm.com> <PIA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1248787500274> <BEA-000447> <Native IO Disabled. Using Java IO.>
I set NativeVersionEnabled to False in nodemanager.properties as specified in the BEA documentation, but can get Native IO to work. The log file clearly indicates that the JDK version is 32-bit:
java.fullversion = J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20071007 (JIT enabled)
Any ideas how to fix this or is this working as designed for AIX platforms?
Thanks!
-Mary Manchukian

The following document asks to set NativeVersionEnabled to False:
http://edocs.bea.com/wls/docs61/adminguide/remotestart.html#1043956:
The Node Manager is available for use only on Windows and UNIX platforms. Native libraries are available for running the Node Manager on Windows, Solaris, HP-UX, AIX and Red Hat Linux operating systems. For UNIX operating systems other than Solaris and HP UX, you will need to use the following argument on the java command line when starting the Node Manager:
-Dweblogic.nodemanager.nativeVersionEnabled=false
If we do not set NativeVersionEnabled to False, the managed server doesn't start at all and fails with the error:
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:296)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:511)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:810)
All I want is to be able to start the managed server from the Admin Console > Remote Start tab.
Thanks,
-Mary

500 "Server error" when use User Management Console

Hello All, i'm staring with Hyperion products on this week))
I installed Shared Serveces and Essbase – System 9
I deployed Shared Serveces on OAS 10.1.3.1
And now when I use User Management Console and try to open
node 'Projects' I get an error 500 "Server error".
Why ?
Please help me resolve this issue
What's wrong? May be I have to install additional components to use Projects?

I found follow error in my OC4J where deployed "User Management Console"
log file located in $OAS_ORACLE_HOME/j2ee/Hyperion/application-deployments/SharedServices9/Hyperion_default_group_1/application.log
07/11/16 10:57:16.633 interop: Error preloading servlet
javax.servlet.ServletException: Error instantiating servlet 'integration'. Servlet class com.hyperion.interop.webservices.integration.IntegrationWebservice not found in web-application interop
     at com.evermind.server.http.HttpApplication.servletClassNotFound(HttpApplication.java:4866)
     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4832)
     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4734)
     at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4922)
     at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1134)
     at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:738)
     at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
     at com.evermind.server.Application.getHttpApplication(Application.java:545)
     at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
     at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1909)
     at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:645)
     at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
     at com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
     at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
     at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2450)
     at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:998)
     at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
     at java.lang.Thread.run(Thread.java:595)
07/11/16 10:57:17.334 interop: Error preloading servlet
javax.servlet.ServletException: Cannot initialize Hyperion DSF. Error:
     Missing class: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
     Dependent class: com.hyperion.workflow.engine.server.services.modelrepository.WfProductSchemaParser
     Loader: SharedServices9.web.interop:0.0.0
     Code-Source: /u0/SOA/SOA_Suite/j2ee/Hyperion/applications/SharedServices9/interop/WEB-INF/lib/wf_eng_server.jar
     Configuration: WEB-INF/lib/ directory in /u0/SOA/SOA_Suite/j2ee/Hyperion/applications/SharedServices9/interop/WEB-INF/lib
The missing class is not available from any code-source or loader in the system.
     at com.hyperion.dsf.server.framework.DsfServer.init(DsfServer.java:52)
     at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2361)
     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4810)
     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4734)
     at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4922)
     at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1134)
     at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:738)
     at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
     at com.evermind.server.Application.getHttpApplication(Application.java:545)
     at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
     at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1909)
     at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:645)
     at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
     at com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
     at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
     at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2450)
     at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:998)
     at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
     at java.lang.Thread.run(Thread.java:595)
07/11/16 10:57:17.482 interop: 10.1.3.1.0 Started

Very weird issue with server logging when using log4j.properties file

I'm using log4j logging. In log4j.properties the root logger is set up to use the ServerLoggingAppender class so that all our application logs go to the main server logfile. In addition, there are several appenders defined for specific components, with output going to specific per-component log files. Everything is going fine until I launch the server console. At this point all of those per-component log files get wiped out (zero length) and some non-ASCII lines are written to at least one of these files, after which the logs appear to be fine. The main server log file does not appear to be affected (because the root logger is set to "warn" level, while component-specific loggers are set to trace, the contents in these files is different; however I tried disabling all the other appenders and turning the root logger up to trace, and that still did not re-create the problem in the main server log file.
And here's the really weird part -- if I use the same configuration, but in a log4j.xml file, the problem does not happen.

Figured it out.
We were passing in the configuration for log4j as -Dlog4j.configuration=file:/<properties file> and this was added to the command line for both the managed and admin servers. Problem is that the console app starts its own instance of log4j, and when it reads the configuration for the appenders it initializes or rolls over the files. At some point we have two JVMs accessing the same files, so some corruption is bound to happen.
I'm not clear why the .xml file made a difference, but earlier we had been passing the log4j configuration as a jar file placed in the domain/lib folder, so perhaps the designer reverted to that (placed the log4j.xml file in a jar in lib, and not simply changed the -Dlog4j.configuration=file:/ option.

Error 500--Internal Server Error when using BI Publisher within OBIEE 11g

I'm using OBIEE 11.1.1.6.2BP1 on a Linux x86-64 server and it has been working just fine. We recently started playing around with the BI Publisher component of that installation and every time i go to http://hostname:port/xmlpserver and try to log in with an Administrator username and password, the following error shows up:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
*10.5.1 500 Internal Server Error*
The server encountered an unexpected condition which prevented it from fulfilling the request.
I have looked around for solutions and tried a couple of them (created a new Admin user in Weblogic Console and checked the opmnctl status) and they did not help. I'm looking for an answer other than upgrade to the latest and greatest
Any help is appreciated.

Do you have any SSO setup as that might be preventing the ability of the user to log into BI Publisher, hence the Internal 500 error message.
Are you using FMW security model for BIP and OBIPS integration which is by default. Check the xmlp-server-config.xml file from the repository [\Middleware\Oracle_BI1\clients\bipublisher\repository\Admin\Configuration\xmlp-server-config.xml] and see what your security model is pointing to?
Also what happens when you try to access from Administration>BI Publisher >Manager BI Publisher ?
Follow : http://docs.oracle.com/cd/E23943_01/bi.1111/e22255.pdf
Oracle Fusion MiddlewareAdministrator's Guide for Oracle Business Intelligence Publisher 11g Release 1
HTH,
SVS

Server Crashes when using Cursor Vars in Stored Procedure

Can anyone make a suggestion
We are experiencing a problem that causes our Weblogic Server to crash
when a JDBC call is made to our Oracle database.
Host Details
Operating System: Solaris Version 8
SunOS 5.8 Generic_108528-15 sun4u sparc SUNW,UltraAX-i2
WebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
JDBC Driver Weblogic JDriver for Oracle
The jdbc command that causes the problem is similar the spcursor
example code file:
// Here we prepare a CallableStatement using a WebLogic extension
// to JDBC that supports binding an Oracle cursor to an output
// parameter. Register the output parameter type as OTHER . . .
cstmt =
(weblogic.jdbc.common.OracleCallableStatement)conn.prepareCall("BEGIN
OPEN ? FOR select * from emp; END;");
cstmt.registerOutParameter(1, java.sql.Types.OTHER);
The crash happens when the re.next() method is invoked after the
execute()
This is the core dump message that is generated:
An unexpected exception has been detected in native code outside the
VM.
Unexpected Signal : 11 occurred at PC=0xd339f37c
Function name=kpcxk2u
Library=/u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
Current Java thread:
at weblogic.db.oci.OciCursor.arrayFetch(Native Method)
at weblogic.db.oci.OciCursor.oci_arrayFetch(OciCursor.java:2002)
at weblogic.jdbc.oci.ResultSet.next(ResultSet.java:759)
at weblogic.jdbc.pool.ResultSet.next(ResultSet.java:180)
at weblogic.jdbc.rmi.internal.ResultSetImpl.next(ResultSetImpl.java:132)
at weblogic.jdbc.rmi.internal.ResultSetImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x10000 /opt/bea/jdk131/jre/bin/../bin/sparc/native_threads/java
0xff350000 /usr/lib/libthread.so.1
0xff390000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff330000 /usr/platform/SUNW,UltraAX-i2/lib/libc_psr.so.1
0xfe480000 /opt/bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
0xff2e0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff310000 /usr/lib/libw.so.1
0xff0b0000 /usr/lib/libmp.so.2
0xff080000 /opt/bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000 /opt/bea/jdk131/jre/lib/sparc/libverify.so
0xfe440000 /opt/bea/jdk131/jre/lib/sparc/libjava.so
0xff020000 /opt/bea/jdk131/jre/lib/sparc/libzip.so
0xfe230000 /opt/bea/jdk131/jre/lib/sparc/libnet.so
0xfe160000 /usr/lib/nss_files.so.1
0xd3700000 /opt/bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoci37.so
0xd3000000 /u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
0xfd090000 /usr/lib/libC.so.5
0xfd3b0000 /u01/app/oracle/product/8.1.7/lib/libwtc8.so
0xfd070000 /usr/lib/libgen.so.1
0xfd050000 /usr/lib/libsched.so.1
0xfd020000 /usr/lib/libaio.so.1
0xfafd0000 /opt/bea/wlserver6.1/lib/solaris/libmuxer.so
Local Time = Thu Apr 3 10:39:37 2003
Elapsed Time = 178
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode)
# An error report file has been saved as hs_err_pid7599.log.
# Please refer to the file for further information.
Abort - core dumped
TIA
Tony

Tony,
"Tony Ross" <[email protected]> wrote in message
news:[email protected]...
Thanks Mitesh for your response.
We have followed your advice on using the 901 driver and updating the
config.xml file. Alas it has not stopped the Solaris WLS from
crashing.Actually, Mitesh sugested you replacing weblogic driver
with oracle one. As it follows from the stacktrace, it has
not been done.
I'd also recommend moving to oracle thin driver as it
doesn't have native code thus is more stable.
Regards,
Slava Imeshev
In addition to this we tried using WLS 6.1 SP2 on a Win2000 box
(connecting to same database). We managed to crash this instance as
well. The core dump is as follows:
An unexpected exception has been detected in native code outside the
VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at
PC=0x6021bc08
Function name=kpcxk2u
Library=C:\Oracle\Ora81\BIN\oracommon8.dll
Current Java thread:
at weblogic.db.oci.OciCursor.arrayFetch(Native Method)
- locked <2956f78> (a weblogic.db.oci.OciCursor)
at weblogic.db.oci.OciCursor.oci_arrayFetch(OciCursor.java:2022)
at weblogic.jdbc.oci.ResultSet.next(ResultSet.java:759)
- locked <3423480> (a weblogic.db.oci.OciConnection)
at weblogic.jdbc.rmi.internal.ResultSetImpl.next(ResultSetImpl.java:133)
at weblogic.jdbc.rmi.internal.ResultSetImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x00400000 - 0x00405000 c:\bea\jdk131\bin\java.exe
0x77F80000 - 0x77FFB000 C:\WINNT\System32\ntdll.dll
0x77DB0000 - 0x77E0D000 C:\WINNT\system32\ADVAPI32.dll
0x77E80000 - 0x77F36000 C:\WINNT\system32\KERNEL32.DLL
0x77D30000 - 0x77DA1000 C:\WINNT\system32\RPCRT4.DLL
0x78000000 - 0x78046000 C:\WINNT\system32\MSVCRT.dll
0x6D420000 - 0x6D4EE000 c:\bea\jdk131\jre\bin\hotspot\jvm.dll
0x77E10000 - 0x77E75000 C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000 C:\WINNT\system32\GDI32.DLL
0x77570000 - 0x775A0000 C:\WINNT\System32\WINMM.dll
0x6D220000 - 0x6D227000 c:\bea\jdk131\jre\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 c:\bea\jdk131\jre\bin\verify.dll
0x6D250000 - 0x6D266000 c:\bea\jdk131\jre\bin\java.dll
0x6D3C0000 - 0x6D3CD000 c:\bea\jdk131\jre\bin\zip.dll
0x6D2A0000 - 0x6D2BB000 c:\bea\jdk131\jre\bin\jdwp.dll
0x6D1D0000 - 0x6D1D5000 c:\bea\jdk131\bin\dt_socket.dll
0x75030000 - 0x75043000 C:\WINNT\System32\ws2_32.dll
0x75020000 - 0x75028000 C:\WINNT\System32\WS2HELP.DLL
0x74FD0000 - 0x74FED000 C:\WINNT\system32\msafd.dll
0x75010000 - 0x75017000 C:\WINNT\System32\wshtcpip.dll
0x6D340000 - 0x6D348000 C:\bea\jdk131\jre\bin\net.dll
0x75050000 - 0x75058000 C:\WINNT\System32\WSOCK32.dll
0x782C0000 - 0x782CC000 C:\WINNT\System32\rnr20.dll
0x77980000 - 0x779A4000 C:\WINNT\System32\DNSAPI.DLL
0x77340000 - 0x77353000 C:\WINNT\System32\iphlpapi.dll
0x77520000 - 0x77525000 C:\WINNT\System32\ICMP.DLL
0x77320000 - 0x77337000 C:\WINNT\System32\MPRAPI.DLL
0x75150000 - 0x75160000 C:\WINNT\System32\SAMLIB.DLL
0x75170000 - 0x751BF000 C:\WINNT\System32\NETAPI32.DLL
0x77BE0000 - 0x77BEF000 C:\WINNT\System32\SECUR32.DLL
0x751C0000 - 0x751C6000 C:\WINNT\System32\NETRAP.DLL
0x77950000 - 0x7797A000 C:\WINNT\system32\WLDAP32.DLL
0x77A50000 - 0x77B45000 C:\WINNT\system32\OLE32.DLL
0x779B0000 - 0x77A4B000 C:\WINNT\system32\OLEAUT32.DLL
0x773B0000 - 0x773DE000 C:\WINNT\System32\ACTIVEDS.DLL
0x77380000 - 0x773A2000 C:\WINNT\System32\ADSLDPC.DLL
0x77830000 - 0x7783E000 C:\WINNT\System32\RTUTILS.DLL
0x77880000 - 0x7790D000 C:\WINNT\System32\SETUPAPI.DLL
0x77C10000 - 0x77C6E000 C:\WINNT\System32\USERENV.DLL
0x774E0000 - 0x77512000 C:\WINNT\System32\RASAPI32.DLL
0x774C0000 - 0x774D1000 C:\WINNT\System32\RASMAN.DLL
0x77530000 - 0x77552000 C:\WINNT\System32\TAPI32.DLL
0x71730000 - 0x717BA000 C:\WINNT\system32\COMCTL32.DLL
0x70BD0000 - 0x70C20000 C:\WINNT\system32\SHLWAPI.DLL
0x77360000 - 0x77379000 C:\WINNT\System32\DHCPCSVC.DLL
0x777E0000 - 0x777E8000 C:\WINNT\System32\winrnr.dll
0x777F0000 - 0x777F5000 C:\WINNT\System32\rasadhlp.dll
0x10000000 - 0x10055000
C:\bea\wlserver6.1\bin\oci901_8\weblogicoci37.dll
0x0DE20000 - 0x0DE3A000 C:\Oracle\Ora81\BIN\OCI.dll
0x780A0000 - 0x780B2000 C:\WINNT\System32\MSVCIRT.dll
0x60400000 - 0x60502000 C:\Oracle\Ora81\BIN\OraClient8.Dll
0x60600000 - 0x60682000 C:\Oracle\Ora81\BIN\oracore8.dll
0x60800000 - 0x60848000 C:\Oracle\Ora81\BIN\oranls8.dll
0x0DE40000 - 0x0DE46000 C:\Oracle\Ora81\BIN\oravsn8.dll
0x60200000 - 0x60264000 C:\Oracle\Ora81\BIN\oracommon8.dll
0x60000000 - 0x6011F000 C:\Oracle\Ora81\BIN\orageneric8.dll
0x60350000 - 0x60356000 C:\Oracle\Ora81\BIN\orawtc8.dll
0x60A00000 - 0x60A2B000 C:\Oracle\Ora81\BIN\oranl8.dll
0x60B00000 - 0x60BAA000 C:\Oracle\Ora81\BIN\oran8.dll
0x60E00000 - 0x60E10000 C:\Oracle\Ora81\BIN\orancrypt8.dll
0x61100000 - 0x61137000 C:\Oracle\Ora81\BIN\oranro8.dll
0x0DE50000 - 0x0DEAE000 C:\Oracle\Ora81\BIN\orannzsbb8.dll
0x61500000 - 0x6150E000 C:\Oracle\Ora81\BIN\oranldap8.dll
0x61700000 - 0x6171C000 C:\Oracle\Ora81\BIN\oraldapclnt8.dll
0x61900000 - 0x61906000 C:\Oracle\Ora81\BIN\oranhost8.dll
0x62100000 - 0x62106000 C:\Oracle\Ora81\BIN\oranoname8.dll
0x0DEB0000 - 0x0DEB6000 C:\Oracle\Ora81\BIN\orancds8.dll
0x62300000 - 0x62306000 C:\Oracle\Ora81\BIN\orantns8.dll
0x62500000 - 0x62508000 C:\Oracle\Ora81\BIN\orannds8.dll
0x0DEC0000 - 0x0DEDC000 C:\Oracle\Ora81\BIN\orannms8.dll
0x62700000 - 0x62741000 C:\Oracle\Ora81\BIN\ORATRACE8.dll
0x62900000 - 0x62B1B000 C:\Oracle\Ora81\BIN\orapls8.dll
0x63100000 - 0x63108000 C:\Oracle\Ora81\BIN\oraslax8.dll
0x63200000 - 0x63272000 C:\Oracle\Ora81\BIN\orasql8.dll
0x64700000 - 0x6470C000 C:\Oracle\Ora81\bin\orantcp8.dll
0x64500000 - 0x6450D000 C:\Oracle\Ora81\bin\orannts8.dll
0x75500000 - 0x75504000 C:\WINNT\System32\security.dll
0x782D0000 - 0x782EE000 C:\WINNT\system32\msv1_0.dll
0x11260000 - 0x11265000 C:\bea\wlserver6.1\bin\wlntio.dll
0x77920000 - 0x77943000 C:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000 C:\WINNT\system32\DBGHELP.dll
0x690A0000 - 0x690AB000 C:\WINNT\System32\PSAPI.DLL
Local Time = Thu Apr 03 17:31:00 2003
Elapsed Time = 327
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1_01 interpreted mode)
So now we have a situation where - we can crash either server with a
call to a function. We can now run the spcursors.java example without
problem. The procedure that does crash the WLS can be run successfully
from within sqlplus (it involves multiple subqueries and outer joins).
FYI - the cursors we are returning in the function are weak cursor
types (TYPE ref_cursor IS REF CURSOR)
Any other suggestions greatly welcomed.
Tony
Mitesh Patel <[email protected]> wrote in message
news:<[email protected]>...
Please do the following:
Make sure you have login delay sec=1 for connection pool in config.xml
Should have TestConnOnReserve=true
and use 901 driver instead of 817 driver. Using suggested driver, stillyou can connect to
your original database.
Thanks,
Mitesh
Tony Ross wrote:
Can anyone make a suggestion
We are experiencing a problem that causes our Weblogic Server to crash
when a JDBC call is made to our Oracle database.
Host Details
Operating System: Solaris Version 8
SunOS 5.8 Generic_108528-15 sun4u sparc SUNW,UltraAX-i2
WebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
JDBC Driver Weblogic JDriver for Oracle
The jdbc command that causes the problem is similar the spcursor
example code file:
// Here we prepare a CallableStatement using a WebLogic extension
// to JDBC that supports binding an Oracle cursor to an output
// parameter. Register the output parameter type as OTHER . . .
cstmt =
(weblogic.jdbc.common.OracleCallableStatement)conn.prepareCall("BEGIN
OPEN ? FOR select * from emp; END;");
cstmt.registerOutParameter(1, java.sql.Types.OTHER);
The crash happens when the re.next() method is invoked after the
execute()
This is the core dump message that is generated:
An unexpected exception has been detected in native code outside the
VM.
Unexpected Signal : 11 occurred at PC=0xd339f37c
Function name=kpcxk2u
Library=/u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
Current Java thread:
at weblogic.db.oci.OciCursor.arrayFetch(Native Method)
atweblogic.db.oci.OciCursor.oci_arrayFetch(OciCursor.java:2002)
at weblogic.jdbc.oci.ResultSet.next(ResultSet.java:759)
at weblogic.jdbc.pool.ResultSet.next(ResultSet.java:180)
atweblogic.jdbc.rmi.internal.ResultSetImpl.next(ResultSetImpl.java:132)
atweblogic.jdbc.rmi.internal.ResultSetImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:
atweblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x10000/opt/bea/jdk131/jre/bin/../bin/sparc/native_threads/java
0xff350000 /usr/lib/libthread.so.1
0xff390000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff330000 /usr/platform/SUNW,UltraAX-i2/lib/libc_psr.so.1
0xfe480000 /opt/bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
0xff2e0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff310000 /usr/lib/libw.so.1
0xff0b0000 /usr/lib/libmp.so.2
0xff080000 /opt/bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000 /opt/bea/jdk131/jre/lib/sparc/libverify.so
0xfe440000 /opt/bea/jdk131/jre/lib/sparc/libjava.so
0xff020000 /opt/bea/jdk131/jre/lib/sparc/libzip.so
0xfe230000 /opt/bea/jdk131/jre/lib/sparc/libnet.so
0xfe160000 /usr/lib/nss_files.so.1
0xd3700000/opt/bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoci37.so
0xd3000000 /u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
0xfd090000 /usr/lib/libC.so.5
0xfd3b0000 /u01/app/oracle/product/8.1.7/lib/libwtc8.so
0xfd070000 /usr/lib/libgen.so.1
0xfd050000 /usr/lib/libsched.so.1
0xfd020000 /usr/lib/libaio.so.1
0xfafd0000 /opt/bea/wlserver6.1/lib/solaris/libmuxer.so
Local Time = Thu Apr 3 10:39:37 2003
Elapsed Time = 178
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode)
# An error report file has been saved as hs_err_pid7599.log.
# Please refer to the file for further information.
Abort - core dumped
TIA
Tony

Server Exception when using JDBC to Connect with SAP

Hello,
I am trying to connect to a view in an external database using JDBC. When I run the TestJDBC Tool, I get the following server exception:
com.microsoft.sqlserver.jdbc.SQLServerException: ?? ?? '<view_name>'?(?) ???????.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
   at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
   at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(Unknown Source)
   at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getColumns(JDBCModel.java:202)
   at com.sap.ip.bi.sdk.trialarea.connector.servlet.controller.Control3.doPost(Control3.java:25)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
   at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
   at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
   at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
   at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
   at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
   at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
   at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
   at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
   at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
   at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
   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:104)
   at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
The question marks really make it difficult to determine exactly what the issue is.
Is there a way to perform a trace or to determine what is going on? Our third party provider has already confirmed that the authorization they provided is correct and is working.
Thanks!

Yes you can run a profiler trace on the SQL Server and include the "User Error Message" event under "Errors and Warnings". This will show you the error message that SQL Server is sending to the client.
When you get it, post it here because this is might be a bug in our JDBC driver that it does not turn that error into a sensible com.microsoft.sqlserver.jdbc.SQLServerException.
David
David http://blogs.msdn.com/b/dbrowne/

What is the best way to detect loss of OPC Server connection when using DSC Tags?

I'm using the DSC Module on a new project and I'm pretty impressed so far. The HMI Wizard has saved me quite a bit of time.
My application is configured where the DSC Tags are connected to remote OPC Server Tags.
The issue I'm having is that I cannot detect a loss of the OPC Server when the application is running. Read's of the front panel controls/indicators still return values and the little "connection" icon next them is still green. Even if the connection icon turned red it wouldn't help since the Front Panel is not visible when the main application is running. It is a Sub-VI that's in charge of OPC Data Interfacing. The rest of the application uses the data from the OPC Sub-
VI.
I cannot effect a change on the OPC Servers, so I need a method of detection when the Server is lost on my end.
Any ideas on the best way to do this?
Thanks,
Jim

Hi Jim,
Ideally, error-reporting and -handling should be the way to handle this. However, if errors are not reported/handled as is sometimes the case with OPC, a quick-n-dirty way to do this would be to check for a "heartbeat" signal from your OPC Server. This could be a boolean tag which toggles On and Off (or a counter ticking). You then read this Tag in DSC in a slow loop using the Read Tag VI (not the front-panel control). And keep track of the Changed? output from this Read Tag VI.
As long as the 'Changed?' output is true, you are receieving data from the OPC Server, and hence it's alive. You may add some deadband logic to wait for a specific period of time before declaring the Server's really dead!
Hope this helps,
K
halid

Application server crashes when using JCO

Hi,
I am currently dealing with JCO Version 2.1.8.
For testing purposes, I want to receive data from a Remote Function Module existing in our SAP development system.
Therefore I created a simple Java servlet:
public class POA_EDS_Servlet extends HttpServlet {
   private static final long serialVersionUID = 1L;
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
   response.setContentType("text/html");
   PrintWriter out = response.getWriter();
   out.println("<html>");
     protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
     response.setContentType("text/html");
     PrintWriter out = response.getWriter();
     String uri = request.getParameter("uri");
     JCO.Client connection;
     connection = JCO.createClient("200",
               "DAHMSMA",
               "EN",
               "vmw3063.wdf.sap.corp",
                              "00");
     try {
        connection.connect();
     catch (Exception ex) {
          ex.printStackTrace();
          System.exit(1);
After deploying and when running this servlet, the application server is crashing. That means I have to restart the server via Remote Desktop Connection.
Can anybode provide some help?
Regards
Marco
Edited by: Marco Dahms on Sep 8, 2009 3:30 PM
Edited by: Marco Dahms on Sep 8, 2009 3:33 PM

Hello there,
Can you please paste your defaultrace.log here. This log file will show the exception occured before the crash.
For better debugging always using a logging mechanism and log the messages to a particular file.
Regards,
Vivek

Hardcoded BAM server parameters when using BAM sensors

The problem we're having is that when a BPEL process has BAM sensors, the BAM server configuration parameters are hardcoded in bpel.xml and sensorAction.xml.
This causes problems when the process is being deployed to a different instance than the development instance.
I solved the problem for the bpel.xml file with the <customize> ant task, but haven't found a solution yet for sensorAction.xml.
Any suggestions?
Thanks,
Arnold van Koppen

See..when the BAM Server is down the corresponding data objects wont be available to you..During the design time wat u do is create a variable which contains the elements dat u wanna monitor in the BAM...IN BAM u create data objects ..then u map the schema from the BPEL to the BAM Data Objects ...U need a BAM Server connection which pulls up the metadata from the server ..If the BAM Server is down u wont get the BAM DOs...to keep a back up u can use DB as the sensor action so that the data from the sensor action is written to the DB..Using a DB Adapter i think the data from the Reports schema can be written to the OracleBAM schema ...so that even if the BAM Server is down the data is written to the OracleBAM schema

500 internal server error when using attendance in ESS

Hi All,
when the user clicks on attendance & its related activities in ESS, the following error is displaying frequently and after sometime it is working properly. why it is giving error frequently and how to avoid this error permanently?
Related Activities
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
... 69 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:12:34[UTC], changelist=421181, host=pwdfm101), build date: Tue Oct 16 13:15:01 BST 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Session & Other
Session Locale en_GB
Time of Failure Thu Jan 24 11:58:41 GMT 2008 (Java Time: 1201175921417)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to read deployment descriptor.
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:297)
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getPart(AbstractDeployableObject.java:214)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObjectPart(DeployableObjectFactory.java:113)
at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObjectPart(WDDeployableObject.java:62)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:921)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createVACComponentUsage(FPMComponent.java:745)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:562)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:723)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to find deployment descriptor '.\temp\webdynpro\public\sap.com\msseeproarchiveddocuments\webdynpro\portalapp.xml' on the file system. Please check if the application 'sap.com/msseeproarchiveddocuments' is deployed correctly.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:278)
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:259)
... 58 more
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Unexpected IO exception on GET<sap.com/msseeproarchiveddocuments>
at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:209)
at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeploymentDescriptor(WebDynproRuntimeServiceImpl.java:354)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:274)
... 59 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
at com.sap.engine.services.webdynpro.PApplication.load(PApplication.java:142)
at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:204)
... 61 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
... 65 more
Thanks in advance,
v

Hi,
We were also having the same problem; but we couldnt find a specific solution for that problem.
But when we upgraded the ESS support packages to SP13 for some other reason this issue was also got resolved.
May be helpful i guess.
Regards,
Vijay

500 internal server error when using the web interface

I've created several tables in Visual Studio, and I'm using a .NET backend for my mobile services.
The table code looks something like this...
using Microsoft.WindowsAzure.Mobile.Service;
namespace AzureService.DataObjects
public class Country : EntityData
public string Name { get; set; }
I then added a scaffolded item to generate the controller for my table, then published.
I then went to my azure service, flipthechipservice.azure-mobile.net, and tried to run the default POST with default data.
I then get back a popup, which looks like the following...
Now what baffles me is I have already created another table, called 'Call', which has exactly the same 'Name' field as the above Country table, yet the Call POSTs work.
I then tried creating another table, with a Name field, and I get the 500 error again.
How can this be possibly happening? Nothing is different, and now I get 500 errors?
This makes no sense.
Thanks

Thank you, I looked at the logs, and this is the error...
System.NotSupportedException: Model compatibility cannot be checked because the database does not contain model metadata. Model compatibility can only be checked for databases created using Code First or Code First Migrations.
at System.Data.Entity.Internal.ModelCompatibilityChecker.CompatibleWithMode
I looked this error up, and tried
this proposed solution on StackOverFlow
I changed the line of code in my WebApiConfig Register() method from...
Database.SetInitializer(new MobileServiceInitializer());
to
Database.SetInitializer<MobileServiceContext>(new DropCreateDatabaseIfModelChanges<MobileServiceContext>());
I also have this in my WebApiConfig...
public class MobileServiceInitializer : DropCreateDatabaseIfModelChanges<MobileServiceContext>
protected override void Seed(MobileServiceContext context)
base.Seed(context);
My understanding is that the database should drop and create if the model changes? So why is this not happening?
I then tried another solution, and changed DropCreateDatabaseIfModelChanges to DropCreateDatabaseAlways. I still get an internal error. Then the logs show this problem...
System.Data.SqlClient.SqlException (0x80131904): Cannot open database "master" requested by the login. The login failed.
Login failed for user 'QEOzFqAnDXLogin_flipthechipservice'.
This session has been assigned a tracing ID of 'a3b12e78-90f2-4db0-a5ca-6895eebd246c'. Provide this tracing ID to customer support when you need assistance.
at System.Data.SqlClient.SqlInternalConnection.OnError
As an additional question, how do I re-generate my local SQL database when debugging on my local PC's web browser? I deleted the database, but can't seem to get it back?
Thanks

"Phantom" Volume created on Server reboot when using SSHDD

10.6.2 Server - 1 X 128MB SSHDD - 3 X 1TB HDD (Raid 5)
System Volume is named: 10.6.2
Raid Array is named: Storage
As you probably know, on reboot, the SSHDD comes up faster than the RAID array. As a result typically a "Phantom" volume (Storage 1 - in my example) is created and mounted that points to an empty directory. Well, I have a new twist on this one. The "Phantom" volume (Storage 1) actually points to the correct files and "Storage" is now an empty folder.
The fix for this one is a bit more complicated than what typically happens, but I'm wondering if anyone knows if Apple has fixed this issue or if it is even possible to fix it?

[email protected] wrote:
Interesting that Apple has not dealt with it since 2008, so I guess there's no hope it will be resolved anytime soon.
There are limits to what Apple can do about this. If a program asks OS X to create a folder, it does so, even if that folder is in /Volumes. For OS X to behave differently, the /Volumes folder would have to be given a special status. You'd have to retain the ability for the disk mounter logic to create entries there as well as whatever deals with disk images, if that's different from the mounter. There may be other cases where routines would need that permission. In any case, I doubt it's a simple fix.
What amazes me is that the issue is not acknowledged when I have called tech support (at least three times) on this issue. You'd think AT LEAST there would be a white paper or document somewhere on how to deal with this (if they are not going to fix it).
That is a little disappointing.

How to retain new line characters when using Node.getNodeValue()

Hi,
I have xml as shown bellow
*<DETAILS>*
this is line one
this is line two
thi is line three
*</DETAILS>*
when I parse this using dom( Node.getNodeValue() ), the value I am getting is as shown bellow
this is line onethis is line twothis is line three
but I wanted as is I have in my xml i.e,
this is line one
this is line two
this is line three
( to show that as is in HTML page)
can some body help me ??
Thanks in advance .

Hi,
You could try this:
replace(your_data, chr(10), '')

Passing arguments to Managed Server ServerStart when using Node Manager

Similar Messages

Maybe you are looking for