Native System Calls
How are native system calls done in Java?
after reading the JNI tutorial, i think this is way to much to do just to perform a simple system call. anyone else know a simpler way to call up an executable program? linux or windows... it doesnt matter
Similar Messages
-
Making Palm System calls using J2ME
Hi is there anyway where I can use the old KJava API or even the J2ME to make system calls such as
DmFindDatabase(0,"Something")
SysAppLaunch(0,dbID,0,cmdPrintChars,theChars,&result);
axlrose82[axlrose82],
At the moment, we are quite certain that the kVM for the PalmOS do not contain any API that allows a developer to make system calls to the PalmOS itself. The CLDC/MIDP specification does not specify any native system calls access any of the native apps. I can see from your code that you are trying to access the Palm database but I'm afraid you are out of luck with the current specs.
HTH.
Allen Lai
Developer Technical Support
SUN Microsystems
http://www.sun.com/developers/support/ -
How to run native system method?
This method definition exists in ObjectInputStream.java:
private static native Object allocateNewObject(Class aclass, Class initclass)
throws InstantiationException, IllegalAccessException;
I want to use this same method. I can compile with the above definition in my source with no problem. When I try to run it I get a dll missing error.
I checked every occurance of loadLibrary in jdk1.3.1 source and found nothing that looks useful.
How do I call this native system method as ObjectInputStream.java does?This is what you need to do:
Create a policy file such as: (Note you can use different permissions that I have, but this was quick and dirty)
grant codeBase "file:./bin/"
permission java.security.AllPermission;
Save file as "java.policy" (or some other name) in your current dir.
Create a test class:
import java.io.ObjectInputStream;
import java.net.InetAddress;
public class Test
public static void main(String[] args)
try
Method m = ObjectInputStream.class.getDeclaredMethod("allocateNewObject", new Class[] {Class.class, Class.class});
System.out.println(m);
m.setAccessible(true);
Object result = m.invoke(null, new Object[] {InetAddress.class, Object.class});
System.out.println(result);
catch (Throwable t)
t.printStackTrace();
Compile and run it:
javac Test.java
java -Djava.security.manager -Djava.security.policy=java.policy -classpath . Test
The output is:
private static native java.lang.Object java.io.ObjectInputStream.allocateNewObject(java.lang.Class,java.lang.Class) throws java.lang.InstantiationException,java.lang.IllegalAccessException
0.0.0.0/0.0.0.0
Any questions, e-mail me.
Eric B. Martin
[email protected] -
Any suggestions how one would perform a UNIX call inside a C++ or Java program?
Student who needs help.If it is really a system call, then you will have to define and implement a "native" method.
o java method witha "native modifier".
o write a small c program that implements the method
If you define the native method, and then run java.h, the result is a header file for the c program. -
- Can I make system calls to access the local file system? If
so, is there a sample?
- Can I make system calls to run local console
scripts/binaries and get the output back? If so, is there a sample?
Thanks,"Greg Lafrance" <[email protected]> wrote in
message
news:gd8flp$sul$[email protected]..
> To be fair, Adobe's initial vision for AIR is not as a
technology that
> would
> permit you to create desktop apps that do all that
"regular" desktop apps
> do.
>
> Part of the reason is because they wanted to have a
solution that "starts"
> to
> blur the lines between online and desktop, but I suspect
another reason is
> because they wanted to get it out the door, and dealing
with the
> additional
> security considerations might delay that.
>
> That said, I'm right there with you, I am looking
forward to when AIR apps
> can
> execute native apps.
>
> One of the problems is that Adobe has "grown up" and now
is getting a
> touch
> stiff, though I still believe they will continue to be
one of the greatest
> software firms out there for the next 5 - 10 - 15+
years.
>
> Of course I work there, so I'm at least a bit biased.
But then again, I am
> a
> bit of a rebel against some aspects of Adobe (and
definitely against some
> aspects of the former Macromedia) culture.
Heh. Been there, done that. They stopped giving me t-shirts -
Posix Perf Pack - Interrupted system call (WL6SP1)
Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)We apparently had quite a bit of premature thread death, about half of our threads
are MIA
"Mike Reiche" <[email protected]> wrote:
>
Ummmm.. so you set the executeThreadCount to what? 55? And PercentSocketReaders
to 50?
And you are missing execute threads 1 through 25. Where did they go?
The only
threads you have left are the ones listening for requests - and they
don't do
any work. Find out what happened to the missing threads.
Mike
"Joe" <[email protected]> wrote:
Here is our thread dump ...just FYI we took a thread dump every minute
for about
5-7 minutes. The thread dump did NOT change
------------------------begin thread dump-----------------------
Full thread dump:
"Thread-4" daemon prio=5 tid=0xc39fb8 nid=0x51 waiting on monitor [0xb3501000..0xb3501a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at javax.mail.EventQueue.dequeue(EventQueue.java:78)
at javax.mail.EventQueue.run(EventQueue.java:97)
at java.lang.Thread.run(Thread.java:484)
"HighPriority TimeEventGenerator" daemon prio=9 tid=0xaa7f30 nid=0x4e
waiting
on monitor [0xb1e81000..0xb1e81a28]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
at java.lang.Thread.run(Thread.java:484)
"SSLListenThread" prio=5 tid=0x5b9ba8 nid=0x4d runnable [0xb2e81000..0xb2e81a28]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:126)
at weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:117)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:247)
"ListenThread" prio=5 tid=0x912768 nid=0x4c runnable [0xb2f81000..0xb2f81a28]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:247)
"ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5
tid=0x2da950
nid=0x49 waiting on monitor [0xb3701000..0xb3701a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5
tid=0x2d9218
nid=0x48 waiting on monitor [0xb3801000..0xb3801a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
prio=5 tid=0x2d88f0
nid=0x47 waiting on monitor [0xb3901000..0xb3901a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
prio=5 tid=0x2d83c8
nid=0x46 waiting on monitor [0xb3a01000..0xb3a01a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"TimeEventGenerator" daemon prio=5 tid=0x379f58 nid=0x45 waiting onmonitor
[0xb3b01000..0xb3b01a28]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
at java.lang.Thread.run(Thread.java:484)
"TimeEventGenerator" daemon prio=5 tid=0x349f58 nid=0x44 waiting onmonitor
[0xb3c01000..0xb3c01a28]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
at java.lang.Thread.run(Thread.java:484)
"SpinnerRandomSource" daemon prio=5 tid=0x419698 nid=0x43 waiting on
monitor [0xb3d01000..0xb3d01a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:92)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:109)
"ExecuteThread: '54' for queue: 'default'" daemon prio=5 tid=0x416740
nid=0x42
waiting for monitor entry [0xb3e01000..0xb3e01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '49' for queue: 'default'" daemon prio=5 tid=0x4130e0
nid=0x3d
waiting for monitor entry [0xb4301000..0xb4301a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '48' for queue: 'default'" daemon prio=5 tid=0x412600
nid=0x3c
waiting for monitor entry [0xb4401000..0xb4401a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '47' for queue: 'default'" daemon prio=5 tid=0x411b20
nid=0x3b
waiting for monitor entry [0xb4501000..0xb4501a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '46' for queue: 'default'" daemon prio=5 tid=0x410a38
nid=0x3a
waiting for monitor entry [0xb4601000..0xb4601a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '45' for queue: 'default'" daemon prio=5 tid=0x40ff58
nid=0x39
waiting for monitor entry [0xb4701000..0xb4701a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '44' for queue: 'default'" daemon prio=5 tid=0x40f478
nid=0x38
waiting for monitor entry [0xb4801000..0xb4801a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '43' for queue: 'default'" daemon prio=5 tid=0x40e998
nid=0x37
waiting for monitor entry [0xb4901000..0xb4901a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '42' for queue: 'default'" daemon prio=5 tid=0x40deb8
nid=0x36
waiting for monitor entry [0xb4a01000..0xb4a01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '41' for queue: 'default'" daemon prio=5 tid=0x40d3d8
nid=0x35
waiting for monitor entry [0xb4b01000..0xb4b01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '40' for queue: 'default'" daemon prio=5 tid=0x40c8f8
nid=0x34
waiting for monitor entry [0xb4c01000..0xb4c01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '39' for queue: 'default'" daemon prio=5 tid=0x40be18
nid=0x33
waiting for monitor entry [0xb4d01000..0xb4d01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '38' for queue: 'default'" daemon prio=5 tid=0x40b338
nid=0x32
waiting for monitor entry [0xb4e01000..0xb4e01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '37' for queue: 'default'" daemon prio=5 tid=0x40a858
nid=0x31
waiting for monitor entry [0xb4f01000..0xb4f01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '36' for queue: 'default'" daemon prio=5 tid=0x409970
nid=0x30
waiting for monitor entry [0xb5001000..0xb5001a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '35' for queue: 'default'" daemon prio=5 tid=0x408e90
nid=0x2f
waiting for monitor entry [0xb5101000..0xb5101a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '34' for queue: 'default'" daemon prio=5 tid=0x4083b0
nid=0x2e
waiting for monitor entry [0xb5201000..0xb5201a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '33' for queue: 'default'" daemon prio=5 tid=0x4078d0
nid=0x2d
waiting for monitor entry [0xb5301000..0xb5301a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '32' for queue: 'default'" daemon prio=5 tid=0x406df0
nid=0x2c
waiting for monitor entry [0xb5401000..0xb5401a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '31' for queue: 'default'" daemon prio=5 tid=0x406310
nid=0x2b
waiting for monitor entry [0xb5501000..0xb5501a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '30' for queue: 'default'" daemon prio=5 tid=0x405830
nid=0x2a
runnable [0xb5601000..0xb5601a28]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '29' for queue: 'default'" daemon prio=5 tid=0x404548
nid=0x29
waiting for monitor entry [0xb5701000..0xb5701a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '28' for queue: 'default'" daemon prio=5 tid=0x403a68
nid=0x28
waiting for monitor entry [0xb5801000..0xb5801a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '27' for queue: 'default'" daemon prio=5 tid=0x402f88
nid=0x27
waiting for monitor entry [0xb5901000..0xb5901a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '26' for queue: 'default'" daemon prio=5 tid=0x4024a8
nid=0x26
waiting for monitor entry [0xb5a01000..0xb5a01a28]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"Signal Dispatcher" daemon prio=10 tid=0xf2320 nid=0x9 runnable [0..0]
"Finalizer" daemon prio=8 tid=0xef678 nid=0x7 waiting on monitor [0xb8b81000..0xb8b81a28]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:149)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
at java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:120)
"Reference Handler" daemon prio=10 tid=0xedd40 nid=0x6 waiting on monitor
[0xfad01000..0xfad01a28]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:129)
"main" prio=5 tid=0x298c0 nid=0x1 waiting on monitor [0xffbee000..0xffbee4cc]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)
"VM Thread" prio=5 tid=0xecae0 nid=0x4 runnable
"VM Periodic Task Thread" prio=10 tid=0xf1020 nid=0x8 runnable
------------------end thread dump------------------------
"Mike Reiche" <[email protected]> wrote:
Post your thread dumps and I'll tell you where it's stuck.
(not in Object.wait())
Mike
Joe" <[email protected]> wrote:
Mike, how sure are you about this? How do you know what the poll
method
does
exactly..it is going into native code
Also, we can see our execute threads getting tied up on this methodfor
quite
some time. Im not sure that you are correct on this.
"Mike Reiche" <[email protected]> wrote:
The threads are not really 'stuck' in PosixSocketMuxer.poll - they
are
waiting
for socket connections such as an http request - that is normal.
Mike
"Joe" <[email protected]> wrote:
Did you get a respose about this one yet? We have seen this error
in
our logfiles,
and have had periodic server hangs (thread dumps show execute threads
stuck in
at weblogic.socket.PosixSocketMuxer.poll(Native Method))
Thanks for any info
-joe
[email protected] (Guillaume Morel) wrote:
Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
WL6SP1 - Posix Perf Pack - Interrupted system call
Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)Hi all,
I run Weblogic 6.0 SP1 on solaris 2.7.
My web application seems to work but randomly, Weblogic seems to
crash.
The logs say the following message.
Any help is welcome! =)
Guillaume
####<Jun 13, 2001 8:49:29 AM GMT+01:00> <Error> <Posix Performance
Pack> <intupc5> <clarify> <ExecuteThread: '12' for queue: 'default'>
<> <> <000000> <Uncaught Throwable in processSockets>
java.io.IOException: error in poll: Interrupted system call
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:371)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
I've modified the linux kernel and created a few new system calls. I would like to be able to call these functions from a java application. Can someone please explain how to make a system call in Java? Thanks for your help.
ChrisAnd you can call those functions directly with Java Native Interface. The Java tutorial has an example where printf is called from Java. Sun also has a book online, hope you'll find it helpful:
http://java.sun.com/docs/books/jni/
JS, MSC, PITA, TTFN.
http://www.acronymfinder.com -
Is system call multithread safe?
Dear all
Is system call are multithread safe?
i want to use system call eg (sysinfo)
is it multithread safe?
if you check man sysinfo
you couldnot find if it is multithread safe or not.
no any statement about it
could any of you give me some hints?what do you mean by, 'would it help'? Help thread safety? No. The method returns quicker because it is native, but it does not impact thread safety (unless you consider a quicker return to some how increase thread safety).
-
Error during installation of ECC6- system call failed
Dear all,
i encounter the error as below during sap installation. its looks like the ID issue, but this id (fbqadm) is using by me to log into the windows. please help me.
thank
ERROR 2009-03-17 10:07:25.583 [syxxsyshlp.cpp:78]
syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
FSL-00001 System call failed. Error 1326 (Logon failure: unknown user name or bad password.
) in execution of system call 'LogonUser' with parameter (fbqadm, SAPFBWDEV01, *******, LOGON32_LOGON_INTERACTIVE,LOGON32_PROVIDER_DEFAULT,&hUserToken), line (1014) in file (synxccuren.cpp).
TRACE 2009-03-17 10:07:25.813 [iaxxejsbas.hpp:408]
handleException<ESyException>()
Converting exception into JS Exception ESyException.
TRACE 2009-03-17 10:07:25.813
Function setMessageIdOfExceptionMessage: modlib.jslib.caughtExceptionproblem fix after reboot the server
-
Error on WAS no. 10054 SAP Basis System: Operating system call
Hi All,
Error on WAS no. 10054 SAP Basis System: Operating system call
we got the following error message in the syslog of the WAS:
SAP Basis System: Operating system call recv failed (error no. 10054)
The system still works. What can we do?
Thanks.
Best Regards,Hi,
Please check the folloiwng notes
Error no. 10054
34116 - Syslog: "Operating System call xxxx failed"
Thanks
Adil -
Correct Forum? CGI and Server behaviour on Solaris at system()-call
Hi to you all,
Do not know if i am in the correct forum, but maybe it is a Webserver problem.
I have Sun ONE Webserver 6.1 running on Solaris.
Craete some CGI`s in C.
Now I have a problem with one CGI, which have to call a Shellscript via system() call.
The Client just calls the CGI with some parameters, which will write the informations in a file with some additional informations from a database, after that, the script should be startet and do some printjobs in the background.
The CGI and the Shell-script is working fine. My Problem is, that the system() call always waits, until the ShellScript has finished, so the Webserver send the "data successful written" site after a couple of minutes, it should send it immeditatly to the client, so the session is closed.
I have tried to put the shellscript in background with "&", also with nohup and a second shell script which justs starts the first script, also with all combinations of nohup and "&" for background process.
also i tried with "pclose(popen(SCRIPT,"W");" to call the script, it is always the same, the session will close only, when the script has been finished.
In an other Forum I found an entry, that , however, IPlanet webserver always will do this in this way. The session will be closed, when all called processes has benn fisnished.
Any Ideas to solve my problem?The web server reads from the CGI program's stdout. It knows the HTTP response is complete when the CGI program closes its stdout.
When you call system(), the child process inherits the CGI program's stdout and keeps it open until it finishes. If you want the child process to run asynchronously from the HTTP response, you should give the child process a new stdout with > /dev/null. (You'll still need to place the child process in the background with &.) Alternatively, you can fork(), close(1), then exec(). -
Tracing what is happening in the connect() system call
I've been playing around with some of the recipies in dtrace today trying to find out why it takes so long to connect from a linux machine to an ultra 5 running sendmail but I'm not having a lot of luck.
The one thing I can find is that the amount of time for the connect system call to return takes a long time. Here's the dtrace script I wrote (borrowing from Bryan Cantrill's blog):
bash-2.05b# cat functiontime.d
#!/usr/sbin/dtrace -s
#pragma D option flowindent
syscall::connect:entry
/execname == "sendmail"/
self->start = vtimestamp;
syscall:::entry,
syscall:::return
/self->start/
trace(vtimestamp - self->start);
syscall::connect:return
/execname == "sendmail"/
self->start = 0;
exit(0);
This is the output:
bash-2.05b# ./functiontime.d
dtrace: script './functiontime.d' matched 454 probes
CPU FUNCTION
0 => connect 0
0 | connect:return 303079
0 <= connect
I know there are other syscalls going on from the time connect enters to the time it returns but I have no idea how to get them to print.
Any ideas how I can make this script more useful to see exactly where sendmail is getting hung up?You might also try something like
#!/usr/sbin/dtrace -s
#pragma D option flowindent
syscall::connect:entry
/execname == "sendmail"/
self->depth = 1;
self->syscallstart = timestamp
fbt:::entry
/self->depth/
self->start[self->depth] = timestamp;
trace(self->start[self->depth++] - self->syscallstart);
fbt:::return
/self->depth/
this->delta = timestamp - self->start[--self->depth];
@func[probefunc] = quantize(this->delta);
printf("delta is %d\n", this->delta);
self->start[self->depth] = 0;
syscall::connect:return
/self->depth/
exit(0);
}This will give you the function call flow inside the kernel along with the following:
- on function entry, a time delta since connect was called
- on function exit, how long we spent in the function
- on return from the connect system call, a list of histograms showing the call times for all functions called
You are probably going to want to redirect the output as it gets big.
Also note, I've written this to give the information only for the first call to connect.
Alan.
Alan Hargreaves - http://blogs.sun.com/tpenta
Senior Technical Support Specialist/VOSJEC Engineer
Product Technical Support (APAC)
Sun Microsystems -
Exchange 2007 SP3 Install on 2008R2 Fails with "The data passed to a system call is too small"
I'm installing Exchange 2007 SP3 onto Server 2008 R2. I have run this install in compatibility mode and in normal install mode with the same results. Error code 3221684346: The data area passed to a system call is too small. I am installing directly from
the SP3 files, this is not an upgrade. What do I have to do to get this to work?
[2/15/2011 7:24:18 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[2/15/2011 7:24:18 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Processing file 'C:\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Registry file name: 'C:\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving ScSetupAtom
[2/15/2011 7:24:18 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] The following 1 error(s) occurred during task execution:
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[2/15/2011 7:24:18 AM] [1] Finished executing component tasks.
[2/15/2011 7:24:18 AM] [1] Ending processing.
[2/15/2011 7:42:08 AM] [0] End of Setup
[2/15/2011 7:42:08 AM] [0] **********************************************I would probably rebuild the host machine. The Exchange installation should occur without any issues, and where a problem does occur that can be an indication of a more widespread problem. Rebuild the machine, reinstall the prerequisites and try again.
Simon.
Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Hello Poster.
I am having the same issue, however it is most likely NOT a host box problem. The above advice is not a fix. I have 3 servers that are cloned with the same setup. 2 were fixed by doing the Vista compatibility trick, this one gave a different error (which
happened to be the same as above). This org was a 5.5 to 2000. to 2003 coexistence with 2007 currently(because the mailbox role won't install). It has something to do with AD or permissions. Server 2008 r2 inherently has problems installing exchange.
Example, having to use vista compatibility to get the mailbox role to install. SP2 patch gives the same error to some people, and also doesn't upgrade the mailbox role properly in some cases. Some people have had luck restarting the IIS admin service, but
that did not solve my copy of this error. I will repost here if I find a solution to this issue...
Same exact setup log for me as well.
[3/4/2011 10:45:51 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Processing file 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Registry file name: 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving ScSetupAtom
[3/4/2011 10:45:51 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] The following 1 error(s) occurred during task execution:
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[3/4/2011 10:45:51 AM] [1] Finished executing component tasks.
[3/4/2011 10:45:51 AM] [1] Ending processing.
Just curious though, how long is your FQDN? Mine is 34 characters plus whatever exchange is adding to it during setup for this particular string. I found a post with the same error for ISA server and some buffer is only 100 characters for a system call.
ERROR_INSUFFICIENT_BUFFER 122 (0x7A) The data area passed to a system call is too small. http://msdn.microsoft.com/en-us/library/ms681382(v=vs.85).aspx Indicates a msft programming problem.
Outsource Technology Inc. MSFT Professional Consultant -
Dear All,
I am getting a below error while doing ehp6 installation on sybase (high availbility )
can any one help me on this..?
An error occurred while processing option SAP Business Suite 7i 2011 > Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > SAP ASE > High-Availability System > Database Instance( Last error reported by the step: System call failed. Error 2 (The system cannot find the file specified. ) in execution of system call 'CreateProcessAsUser' with parameter ( , NULL, Program Files/sapinst_instdir/BS2011/ERP606/AS-ABAP/SYB/HA/DB, &StartupInfo, &ProcessInfo), line (646) in file (d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcchapp.cpp), stack trace: d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\ejscontroller.cpp: 181: EJSControllerImpl::executeScript() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\jsextension.hpp: 1059: CallFunctionBase::call() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\osmod\iaxxbprocess.cpp: 423: CIaOsProcess::start_impl() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcchapp.cpp: 238: CSyChildApplicationImpl::start(false) d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcchapp.cpp: 262: CSyChildApplicationImpl::doStart() .). You can no
Regards,
Letz..Hello Mauricio.
Thanks
Two Thinks:
1.- This error appears precisely in the process of creating SAP users including you mention sidadm:
A.- Execute sapinst
B.- Installation option is chosen
SAP NetWeaver CE Production Edition
Installation Options
High-Availability System
Central Service Instance (SCS)
c.- System ID, Next and appear message error
2.- However, the user manually create sidadm, I gave the permissions you indicate, and the error message is the same
Thanks
Maybe you are looking for
-
I need your help. I am trying to add my verizon email account but my mini ipad is not letting me do it. Any suggestions?
-
Editing AE or Premiere CS4 projects in Audition 3?
Is there a way to import an After Effects CS4 or Premiere CS4 project with muitiple audio tracks/layers into Audition 3 and edit/balance each track individually? Have been using Soundbooth to clean up audio from individual video clips, but want to ba
-
Hi, We have EBS 11.5.9 with 9.2.0.6 database. For the upgrade of EBS to 12.1.3 and database to 11.2.0.3 what are the basic steps? Can we directly upgrade 11.5.9 to 12.1.1? Thanks,
-
What to do if screen is cracked
I got my ipod touch for Christmas and today the screen cracked. What should I do to get it replaced? What is the safest, most cost-effective way to go about this?
-
Hide emarked fund field in ME5xN
Hi, How can I hide the emarked fund (EMF) field in the accounting tab in ME5xN for certain purchase requisitions ? I couldn't find the field within the other standard customizable field in SPRO. Moreover, our programmers claim that the field can't be