Ginga-J Sun specific API's

Hi All,
Am not sure if this is the right to place my query about Ginga API . I did not find any specific forum group where I could post this. Hence this is here.
Am into developing middleware for ginga. Sun has taken up the activity of developing API's for Ginga-J middleware, as there was an issue regarding rights with
DVB consortium. Has anyone got any idea regarding whether any development is going on from the part of Sun and if so at which level is it now?
When will Sun publish the API's ?
Thanks in advance

Hello.
We have received the 1st public release of Ginga-J with a small Java DTV implementation.
Please, read my post:
[http://translate.google.com/translate?prev=hp&hl=pt-BR&js=n&u=http://b4dtv.blogspot.com/2009/06/fisl-10-agora-com-ginga-j-o-novo-com.html&sl=pt&tl=en&history_state0=]
Original, in Brazillian Portuguese:
FISL 10: agora com Ginga-J... o novo, com Java DTV(?)
[http://b4dtv.blogspot.com/2009/06/fisl-10-agora-com-ginga-j-o-novo-com.html]
Regards,
Marcos Henke
http://b4dtv.blogspot.com
http://groups.google.com/devdtv

Similar Messages

Help required to create portal without using any vendor specific API's

Hi All,
I am trying to develope a portal without using any vendor specific API or tool like Weblogic workshop or Vignette Wizard. I would like to know whether Sun Microsystem provides any API for developing portal. I would also appreciate if I can get few links for developing portal using java API's...
Thanks in advance...
Dgk

Sure Sun provides the tools: it is called the compiler. Now all you need to do is write the code for a portal. But since there are vendor specific solutions available that could make your life a lot easier, writing one yourself is like reinventing the wheel.
Pardon my mild sarcasm, but avoiding API's not developed by Sun is not the general idea behind the Java platform. You are encouraged to use those API's.

Exploratory Programming of the Sun IDM API

Exploratory Programming of the Sun IDM API using Rhino
Sun IDM comes with a JavaScript interpreter (Rhino) that can be invoked from the command-line. This gives developers an easy way to explore the large number of classes that comprised the product.
Let's say for example that you need the approvers of a role object in order to display them on a form. (The role view provides this information, but let's ignore this for the purpose of this example.) The role javadoc mentions two methods to get the approvers, getApproverRefs() and getApprovers(). Unfortunately they are not described clearly, and the difference between the two is not clear either.
In order to understand what these methods do and what they return, you can use the interpreter to invoke each one directly.
First start the interpreter with the 'lh.bat js' command:
lh.bat jsYou will be greeted with the javascript prompt "js>"
Then the first thing to do is to login to the application server. Copy-paste the following code into the shell interpreter.
// Java packages are prepended with the word 'Packages'
// and are imported using the 'importPackage' function
importPackage(Packages.com.waveset.util);
importPackage(Packages.com.waveset.object);
importPackage(Packages.com.waveset.security.authn);
importPackage(Packages.com.waveset.session);
importPackage(Packages.com.waveset.ui);
importPackage(Packages.java.util);
// Use arguments[0] and arguments[1] if you want to pass credentials from the command line
// Here we just use the built-in account "configurator"
var epass = new EncryptedData("configurator");
var session = SessionFactory.getSession("configurator", epass);
print("Waveset session established");Alternatively save the above code to a text file called "idm-init.js" and load the file from the interpreter.
js> load("idm-init.js")
Waveset session establishedOnce a session has been established, objects can be loaded from the repository. Enter this line at the prompt to get the role object named "testrole3"
js> var roleObject = session.getObject("Role", "testrole3");Enter the variable name at the prompt to cause the interpreter to invoke the object's 'toString' method.
js> roleObject
Role:testrole3Use a 'for' loop to print out all of the object's method and fields.
js> for (i in roleObject) { print(i) }Enter a method's name to invoke it. Let's call getApproverRefs().
js> var approvers1 = roleObject.getApproverRefs();
js> approvers1
[User:role1approver(id=#ID#1CC1759638D9AF96:182C132:10F3E8040B5:-7FBE), User:role2approver(id=#ID#1CC1759638D9AF96:182C132:10F3E8040B5:-7FB8)]
js> approvers1.get(0).getClass();
class com.waveset.object.ObjectRefNow let's check out getApprovers().
js> var approvers2 = roleObject.getApprovers();
js> approvers2
[Lcom.waveset.object.WSUser;@d3c69c
js> approvers2[0].getClass()
class com.waveset.object.WSUserSo getApproverRefs() returns a list of ObjectRef objects, while getApprover() returns an array of WSUser objects.
In summary the Sun IDM JavaScript interpreter can be used to explore the product's vast API. This article used the role class and its getApprovers() and getApproverRefs() methods as an example for exploratory programming. Other applications include automated testing and administrative scripts.
[email protected]

Yes you can customise IDM it is all available in courses and the manuals also provide some info.
As long as you can write the code you need in java or javascript you can call it from IDM: that could be an interface to you naming app.
Otherwise use the SPML interface if you want to use something else then the GUI. This is also described in the manuals.
WilfredS

Do we still have device specific APIs for MIDP2.0 phones?

Hi everyone,
When I was doing MIDP 1.0 coding, I know there is NokiaUI available to implement full screen canvas etc for Nokia phones
It seems using MIDP 2.0, full screen canvas can be achieved by setFullScreenMode(true).
My question is:
On MIDP2.0 phones, what profile level device specific APIs are available for Nokia or any other phones?
Could an API guru out there shed some lights here?
Many thanks in advance,
QM from London

Thanks, found it:
http://www.j2mepolish.org/devices/devices-nokia-ui.html
Can I say if there is more than 100 phones, there could be 100 device specific APIs????

How to extend AVK to scan for other vendor-specific APIs?

All--
How do I extend AVK to scan for other vendor specific APIs.
I tried adding another <name> element underneath the
appropriate the <unsupported> tag in the asmt-config.xml file,
e.g.
<websphere50>
<supported>
</supported>
<unsupported>
<name>com.ibm.ws.activity.ActivityConstants</name>
.......... other <name> elements were left alone ..........
</unsupported>
</websphere50>
But when I scanned the source code it didn't find an import of that API.
Note: it did find an import of the APIs that were pre-defined in the asmt-
config file; just not the one that I added.
Is adding a <name> to the asmt-config.xml file the right approach?
If so, how does the SourceScan ant task know where to find the asmt-
config.xml file. Currently, I left it in the %JAVKE_HOME%/config folder.
Is that the right place for that file?
Any comments on how to extend AVK to scan for other vendor
specific APIs would be greatly appreciated.

Oops!
Its probably bad form to answer your own question, but after
sending out the original post, I treid:
1. opening a new shell
2. running the %JAVKE_HOME%/bin/javke_setenv.bat
3. then ran the "asant code-scan" from that shell and viola it worked ...
Sorry for any confusion.

Adding 2 byte arrays (6 bytes each ) -any specific API available

hi friends
I m fixed up with a problem .
i want to add to arrays of six bytes each .
how can i go for this .
is there any specific API available for the same.
current method i m using is an function which add first bytes of 2 arrays and then check out if the added value is more then FF its incerments the previous bytes and then start adding the second bytes .
but its a very time consuming way .
is there any specific API available ...... to solve out this problem in a much easier way

i want to add to arrays of six bytes each .Looks like you want to add two 48bit numbers, right?
how can i go for this .
is there any specific API available for the same.No. only 8bit and 16bit number operations are supported (and theoretical 32bit operations).
current method i m using is an function which add
first bytes of 2 arrays and then check out if the
added value is more then FF its incerments the
previous bytes and then start adding the second
bytes .Sounds like the paper & pencil addition method.
but its a very time consuming way.That is a common problem when building "large number arithmetic" functions by using 8bit operations.
From my point of view the only possibility for speeding up your algorithm is using nytes instead of shorts as usually the JavaCard processors are 8bit processors and therefore short/16bit operations are already decomposed into several 8bit operations. The only problem can be that java does not have a carry bit or an number overflow error for detecting if a number gets greater than 0xFF.
Jan

Ignoring Sun proprietary API warning in JDK 1.6.0_13.

We are upgrading our application from JDK 1.5.0_17 to JDK 1.6.0_13 and we get so many warnings regarding Sun proprietary API.
Can someone help me in telling when this API's will be removed from Sun API and is there any problem in using this API's as long as we use JDK 1.6.0_13.
At the same time can u suggest the alternate API's which can be used in place of this.
Warinings :
[javac] D:\eRAM3500_07_04\server\src\globalaccess\SSLTunnelSocketFactory.java:9:
warning: sun.net.www.protocol.http.HttpURLConnection is Sun proprietary API and may be removed in a future release
[javac] import sun.net.www.protocol.http.HttpURLConnection;
[javac] ^
[javac] D:\eRAM3500_07_04\server\src\globalaccess\SSLTunnelSocketFactory.java:111:
warning: sun.net.www.protocol.http.HttpURLConnection is Sun proprietary API and may be removed in a future release
[javac] String s1 = "CONNECT " + s + ":" + i + " HTTP/1.0\n" + "User-Agent: " + HttpURLConnection.userAgent;
[javac] ^
[javac] D:\eRAM3500_07_04\server\src\globalaccess\RedirectGSGRequestThread.java:160:
warning: sun.misc.BASE64Encoder is Sun proprietary API and may be removed in a future release
[javac] s2 = "Basic " + (new BASE64Encoder()).encode(s2.getBytes());
[javac] ^
Any help appreciated.

Can someone help me in telling from which release this Sun API's will be removed. I answered that. No. Nobody can help you. What Sun say here is 'From one release to another, these classes may be removed, or they may be moved from one package to another, and it's fairly likely that their interface (method names and signatures) will change.' There's no statement there that they will be removed, and certainly no implication that there is a single release in which they will all be removed at the same time.
So as of now we can migrate to JDK 1.6.0_13 ignoring warnings msgs. Will there be any problem in still using the same api's?I answered that too.
Does this API's work in JDK 1.7 and from where can I download JDK 1.7?You will have to test it yourself. Google will find it for you.
Is there any alternate API to get the user agent string of sun.net.www.protocol.http.HttpURLConnection.userAgentI answered that. You don't need it in a CONNECT command.

Com.sun.messaging API reference

Does somebody has a link to online com.sun.messaging API reference?

Once you downloaded the product, you have the javadoc in there. You can also have a version of the complete source from here:
https://mq.dev.java.net/
As OpenMQ...
HTH
TE

Req Help for "warning: sun.misc.SignalHandler is Sun proprietary API "

Hi All,
I am getting the below exception when i am building the class. Please guide me and please provide any alternate solution for this.
[javac] main\SignalHandler.java:35: warning: sun.misc.SignalHandler is Sun proprietary API and may be removed in a future release
[javac] implements sun.misc.SignalHandler
[javac] ^
[javac] main\SignalHandler.java:69: warning: sun.misc.Signal is Sun proprietary API and may be removed in a future release
[javac] public void handle( final sun.misc.Signal signal )
[javac] ^
[javac] auditlog\core\AuditLogFileWriter.java:26: warning: com.sun.org.apache.xalan.internal.xsltc.runtime.Hashtable is Sun proprietary API and may be removed in a future release
[javac] public static Hashtable writingStatus=new Hashtable();
[javac] ^
[javac] ftpcommon\ftp\PasswordEnDecrypt.java:156: warning: sun.misc.BASE64Encoder is Sun proprietary API and may be removed in a future release
[javac] return new sun.misc.BASE64Encoder().encode(enc);
[javac] ^
[javac] ftpcommon\ftp\PasswordEnDecrypt.java:182: warning: sun.misc.BASE64Decoder is Sun proprietary API and may be removed in a future release
[javac] byte[] dec = new sun.misc.BASE64Decoder().decodeBuffer(str);
[javac] ^
[javac] ftpcommon\main\SignalHandler.java:57: warning: sun.misc.Signal is Sun proprietary API and may be removed in a future release
[javac] sun.misc.Signal.handle( new sun.misc.Signal(signalName), this );
[javac] ^
[javac] main\SignalHandler.java:57: warning: sun.misc.Signal is Sun proprietary API and may be removed in a future release
[javac] sun.misc.Signal.handle( new sun.misc.Signal(signalName), this );
Thanks & Regards,
Rajeshwar
Edited by: Rajeshwar_Java on Apr 27, 2009 5:31 AM
Edited by: Rajeshwar_Java on Apr 27, 2009 5:32 AM

as corlettk already told you: avoid those API whenever possible.
Regarding your cases:
* SignalHandler: proprietary API, there's not alternative. Use it if you must. Fail gracefully if it isn't there
* Hashtable: seems like you simply picked the wrong one. Use the one in java.util
* Base64 stuff: Plenty of free (BSD licensed) implementations out there, I'm sure there's one in commons-codec as well. Use those instead.

Com.sun.corba.se.impl.orb.ORBImpl is Sun proprietary API and may be removed

hi again,
i have a question
what this means?
com.sun.corba.se.impl.orb.ORBImpl is Sun proprietary API and may be removed in a future release

The message means that you are using stuff that you shouldn't be using. Sun may remove that stuff from future versions of Java which will break your code/application/library.

Looking for an specific API

I'm trying to develop to cellphones, but I'm not beeing able to find the MICROMACHINE api. Can anyone tell me we're it is and how do I install it?

Try here:
http://java.sun.com/products/midp/

Determining the JMXServiceURL for your own JVM

Hello.
I'd like to know how to find the JMXServiceURL of the built-in MBeanServer. In Java 5, I'm using sun.management.ConnectorAddressLink.importFrom(int pid) to determine this, but that means I'm using a non-public, Sun-specific API. In Java 6, we have the new interface javax.management.remote.JMXAddressable, which looks like it might make it possible to find the JMXServiceURL without resorting to a non-public API. However, it isn't obvious how to actually use JMXAddressable to accomplish this goal.
Can someone explain how to use JMXAddressable to simulate the function of sun.management.ConnectorAddressLink.importFrom(int pid)?
Thanks,
-Neil

I have these concerns about starting my own connector programmatically:
1. Additional overhead from multiple connectors running. Some applications, like jconsole, may wind up instantiating the built-in connector, too. How concerned should I be about the additional resources consumed by having two connectors? When using jconsole's Threads panel, I see a number of threads associated with the built-in connector, and I don't really have a sense of how busy these threads are. Should I be concerned about this? (I suspect that this isn't a big deal, but I'm uncertain.)
2. Additional coding complexity. I would want to start the connector programmatically but use an anonymous port. If I'm using an RMI registry, the registry itself would need to use an anonymous port. This means I would need to programmatically create the registry itself with an anonymous port, which as far as I can tell can only be done by creating my own RMI server socket factory which captures the port of the created socket. I then need to manually glue together a JMXServiceURL to register myself in that registry, perform the registration, and then get the JMXServiceURL back. All told, this is at least twice as much code as using the sun.* classes.
3. Creating an RMI registry is a potential security problem because other applications running on the same host can connect to that registry and replace my JMXConnectorServer with their own. I recall a recent blog about securing the RMI registry against this, but the procedure was fairly complicated, further increasing the coding complexity concern above (concern #2). One thing I haven't explored is the possibility of exposing the JMXConnectorServer via RMI but without using an RMI registry, which may be appropriate here because, given that the RMI registry isn't using a well-known port in my case anyway, it isn't really adding any value. Is it possible to expose the JMXConnectorServer via RMI, on an anonymous port, without using an RMI registry and in a way that allows me to discover what port actually gets assigned to it?
4. I noticed that if I start my own JMXConnectorServer manually, it prevents my application from exiting. Is the fix for this to simply call the start() method from within a daemon thread, or do I need to ensure that I call stop()? If I need to call stop(), I may need to set up a shutdown hook to do this.
All told, using the sun.* APIs makes the problem much simpler. I suspect that I may eventually want to move to starting the connector server programmatically, especially as I want to use the security features, but at present the simplicity of the sun.* APIs is too attractive to pass up.
Thanks,
-Neil

Sun One 7 2004Q2 restart on breakpoint in debug

Hi,
I have a very annoying problem.
I took over a project from another team of another company. I have to migrate the web application (using Struts, J2EE, EJB 2.0, ...) from Sun One to JBoss.
For this, a specific profile is searched, and awaiting this profile, i have to get to know the project, structure and code (i don't know any EJB 2.0, i know Hibernate and Spring and like that a lot more than EJB).
Now i'm working a month and a half already on this project, reading documentation, adding documentation, inspecting the code, and developing small changes and bugfixes.
Every time i wanted to perform a remote application debug from within Eclipse to the Sun One AS, things fail.
I start Sun One in debug mode, i check the address port, i connect to that port from Eclipse in debug mode (remote application debug), but when the application reaches the breakpoint, the Sun One AS just restarts, and the application gives a page not found.
First i thought it was a memory problem (i read logs with OutOfMemory and parallel GC errors, but i can't find the logs anymore), and i finally got a computer with 2GB RAM (we work on VPC's). But that didn't solve the problem either.
I removed the -Xmx option for maximum heap size, but that didn't do any good either.
Does anyone know how i can perform debugging from within Eclipse to the Sun One AS without problems?
Thanks very much in advance.

And i found an error log in the /config directory of the used server instance:
# An unexpected error has been detected by HotSpot Virtual Machine:
# Internal Error (50532D41524B33574545500E435050011C), pid=3964, tid=2368
# Java VM: Java HotSpot(TM) Server VM (1.4.2_11-b06 mixed mode)
--------------- T H R E A D ---------------
Current thread (0x00d89968): VMThread [id=2368]
Stack: [0x05900000,0x05a00000)
[error occurred during error reporting, step 110, id 0xc0000005]
[error occurred during error reporting, step 120, id 0xc0000005]
VM_Operation (0x0c5bfbb4): parallel gc failed allocation, mode: safepoint, requested by thread 0x066e1008
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x06eb1008 JavaThread "service-j2ee-2" [_thread_in_native, id=2108]
0x0eb52e00 JavaThread "Thread-54" daemon [_thread_blocked, id=276]
0x070b9110 JavaThread "SingleSignOnExpiration" daemon [_thread_blocked, id=2796]
0x06eb1170 JavaThread "StandardManager[]" daemon [_thread_blocked, id=1804]
0x00f915f8 JavaThread "Thread-53" daemon [_thread_blocked, id=1984]
0x069cfb70 JavaThread "StandardManager[/kwatraWeb]" daemon [_thread_blocked, id=3772]
0x06eccbe0 JavaThread "RMI LeaseChecker" daemon [_thread_blocked, id=2592]
0x06c0dfb8 JavaThread "GC Daemon" daemon [_thread_blocked, id=3680]
0x06e03258 JavaThread "RMI Reaper" [_thread_blocked, id=772]
0x06594dd8 JavaThread "Thread-52" daemon [_thread_blocked, id=2920]
0x06adac70 JavaThread "RMI TCP Accept-0" daemon [_thread_in_native, id=3528]
0x06c3adf8 JavaThread "Thread-51" [_thread_blocked, id=3860]
0x06c3a810 JavaThread "Thread-50" daemon [_thread_blocked, id=2544]
0x0682e5b0 JavaThread "JTS Timeout Thread" daemon [_thread_blocked_trans, id=1964]
0x06789c60 JavaThread "ORB Server-side Reader, conn from MVG-WRK-0041.DG3.be:3019"
daemon [_thread_in_native, id=2236]
0x06c314f8 JavaThread "ORB Client-side Reader, conn to 10.20.24.3:4653" daemon [_thread_in_native, id=132]
0x06eb29c0 JavaThread "Thread-47" [_thread_blocked, id=4008]
0x06d315c0 JavaThread "ORB Listener 0.0.0.0:4653" daemon [_thread_in_native, id=3956]
0x06bb8a40 JavaThread "Thread-46" daemon [_thread_blocked, id=3040]
0x06bb7e30 JavaThread "Thread-45" daemon [_thread_blocked, id=376]
0x067e8c70 JavaThread "Thread-44" daemon [_thread_blocked, id=2968]
0x067e8100 JavaThread "Thread-43" daemon [_thread_blocked, id=2928]
0x067e7518 JavaThread "Thread-42" daemon [_thread_blocked, id=3384]
0x066ebc70 JavaThread "Thread-41" daemon [_thread_blocked, id=3180]
0x066eb100 JavaThread "Thread-40" daemon [_thread_blocked, id=3876]
0x066ea620 JavaThread "Thread-39" daemon [_thread_blocked, id=2372]
0x069505d0 JavaThread "Thread-38" daemon [_thread_blocked, id=3504]
0x0694f930 JavaThread "Thread-37" daemon [_thread_blocked, id=2116]
0x0694ee50 JavaThread "Thread-36" daemon [_thread_blocked, id=3784]
0x06705298 JavaThread "Thread-35" daemon [_thread_blocked, id=3524]
0x06704408 JavaThread "Thread-34" daemon [_thread_blocked, id=3080]
0x06b80b80 JavaThread "Thread-33" daemon [_thread_blocked, id=264]
0x06b80068 JavaThread "Thread-32" daemon [_thread_blocked, id=1020]
0x06787670 JavaThread "Thread-31" daemon [_thread_blocked, id=472]
0x06786a60 JavaThread "Thread-30" daemon [_thread_blocked, id=3464]
0x06a5e1d0 JavaThread "Thread-29" daemon [_thread_blocked, id=2520]
0x06a5d660 JavaThread "Thread-28" daemon [_thread_blocked, id=3804]
0x067773c0 JavaThread "Thread-27" daemon [_thread_blocked, id=2164]
0x06776c50 JavaThread "Thread-26" daemon [_thread_blocked, id=1852]
0x066e22b0 JavaThread "Thread-25" daemon [_thread_blocked, id=3148]
0x066e1b40 JavaThread "Thread-24" daemon [_thread_blocked, id=3828]
0x066e1008 JavaThread "Thread-23" daemon [_thread_blocked, id=3060]
0x069cdc88 JavaThread "Thread-22" daemon [_thread_blocked, id=3708]
0x06994a00 JavaThread "Thread-21" daemon [_thread_blocked, id=960]
0x06993fd0 JavaThread "Thread-20" daemon [_thread_blocked, id=2224]
0x06ae8578 JavaThread "Thread-19" daemon [_thread_blocked, id=2704]
0x06a1c680 JavaThread "Thread-18" daemon [_thread_blocked, id=3892]
0x06ed4ca8 JavaThread "Thread-17" daemon [_thread_blocked, id=1144]
0x06713280 JavaThread "Thread-16" daemon [_thread_blocked, id=3476]
0x0680c080 JavaThread "Thread-15" daemon [_thread_blocked, id=3160]
0x0680ba18 JavaThread "Thread-14" daemon [_thread_blocked, id=1308]
0x066e7f08 JavaThread "Thread-13" daemon [_thread_blocked, id=1652]
0x066e7d10 JavaThread "Thread-12" daemon [_thread_blocked, id=1388]
0x00f816a0 JavaThread "Thread-11" daemon [_thread_blocked, id=2880]
0x066e8868 JavaThread "Thread-10" daemon [_thread_blocked, id=2248]
0x06ac6810 JavaThread "Thread-9" daemon [_thread_blocked, id=3844]
0x066a86e0 JavaThread "Thread-8" daemon [_thread_blocked, id=1192]
0x066a84e8 JavaThread "Thread-7" daemon [_thread_blocked, id=1732]
0x066560d0 JavaThread "Thread-0" [_thread_blocked, id=476]
0x00d9a948 JavaThread "CompilerThread1" daemon [_thread_blocked, id=1256]
0x00d99c40 JavaThread "CompilerThread0" daemon [_thread_blocked, id=408]
0x00d98c98 JavaThread "AdapterThread" daemon [_thread_blocked, id=2640]
0x00d98008 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=2056]
0x00d818c8 JavaThread "JDWP Event Helper Thread" daemon [_thread_in_native, id=1520]
0x00ee7e40 JavaThread "JDWP Transport Listener: dt_socket" daemon [_thread_in_native, id=3712]
0x00d8bb78 JavaThread "Finalizer" daemon [_thread_blocked, id=3688]
0x00d8a768 JavaThread "Reference Handler" daemon [_thread_blocked, id=3624]
0x00d67a18 JavaThread "main" [_thread_in_native, id=2080]
Other Threads:
=>0x00d89968 VMThread [id=2368]
0x00db2630 WatcherThread [id=384]
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x00db4eb0/0x00000600] Threads_lock - owner thread: 0x00d89968
[0x00cf2ba8/0x000005c4] Heap_lock - owner thread: 0x066e1008
Heap
PSYoungGen      total 280768K, used 53248K [0x10010000, 0x27e70000, 0x27e70000)
eden [0x10010000,0x10010000,0x1a610000)
from [0x21240000,0x24640000,0x27e70000)
to   [0x1a610000,0x1a610000,0x21240000)
PSOldGen        total 217536K, used 156605K [0x27e70000, 0x352e0000, 0x4fc10000)
object [0x27e70000,0x3175f7c8,0x352e0000)
PSPermGen       total 44800K, used 44727K [0x4fc10000, 0x527d0000, 0x53c10000)
object [0x4fc10000,0x527bdff8,0x527d0000)
Dynamic libraries:
0x00400000 - 0x00406000      C:\Sun\AppServer7\bin\appservd.exe
0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f4000      C:\WINDOWS\system32\kernel32.dll
0x60b90000 - 0x60c79000      C:\Sun\AppServer7\bin\ns-httpd40.dll
0x60e00000 - 0x60e1a000      C:\Sun\AppServer7\bin\ssl3.dll
0x60ce0000 - 0x60d5d000      C:\Sun\AppServer7\bin\nss3.dll
0x60b10000 - 0x60b17000      C:\Sun\AppServer7\bin\libplc4.dll
0x60ac0000 - 0x60af1000      C:\Sun\AppServer7\bin\libnspr4.dll
0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f01000      C:\WINDOWS\system32\RPCRT4.dll
0x71ad0000 - 0x71ad9000      C:\WINDOWS\system32\WSOCK32.dll
0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
0x77c10000 - 0x77c68000      C:\WINDOWS\system32\msvcrt.dll
0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
0x71a50000 - 0x71a8f000      C:\WINDOWS\system32\MSWSOCK.dll
0x60b20000 - 0x60b26000      C:\Sun\AppServer7\bin\libplds4.dll
0x60c80000 - 0x60c88000      C:\Sun\AppServer7\bin\nsfc.dll
0x60db0000 - 0x60db6000      C:\Sun\AppServer7\bin\nstime.dll
0x60cd0000 - 0x60cda000      C:\Sun\AppServer7\bin\nsprwrap.dll
0x60e20000 - 0x60e2c000      C:\Sun\AppServer7\bin\support.dll
0x60dc0000 - 0x60dc5000      C:\Sun\AppServer7\bin\nstp.dll
0x600e0000 - 0x600e5000      C:\Sun\AppServer7\bin\getprop.dll
0x7e410000 - 0x7e4a1000      C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f57000      C:\WINDOWS\system32\GDI32.dll
0x60b30000 - 0x60b4e000      C:\Sun\AppServer7\bin\libsi18n.dll
0x60aa0000 - 0x60aaa000      C:\Sun\AppServer7\bin\libdbm.dll
0x600a0000 - 0x600a5000      C:\Sun\AppServer7\bin\ares3.dll
0x7c9c0000 - 0x7d1d6000      C:\WINDOWS\system32\SHELL32.dll
0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
0x60da0000 - 0x60da8000      C:\Sun\AppServer7\bin\NSSLDAP32V50.dll
0x60cc0000 - 0x60cc6000      C:\Sun\AppServer7\bin\NSLDAPPR32V50.dll
0x60c90000 - 0x60cb5000      C:\Sun\AppServer7\bin\NSLDAP32V50.dll
0x60e30000 - 0x60ec1000      C:\Sun\AppServer7\bin\xerces-c.dll
0x609e0000 - 0x60a3c000      C:\Sun\AppServer7\bin\icuuc2.dll
0x60100000 - 0x60904000      C:\Sun\AppServer7\bin\icudt2.dll
0x60910000 - 0x609a2000      C:\Sun\AppServer7\bin\icuin2.dll
0x00320000 - 0x00331000      C:\WINDOWS\system32\MSVCIRT.dll
0x773d0000 - 0x774d3000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls
_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
0x5d090000 - 0x5d12a000      C:\WINDOWS\system32\comctl32.dll
0x76f20000 - 0x76f47000      C:\WINDOWS\system32\DNSAPI.dll
0x76fb0000 - 0x76fb8000      C:\WINDOWS\System32\winrnr.dll
0x76f60000 - 0x76f8c000      C:\WINDOWS\system32\WLDAP32.dll
0x76fc0000 - 0x76fc6000      C:\WINDOWS\system32\rasadhlp.dll
0x60a60000 - 0x60a72000      C:\Sun\AppServer7\bin\j2eeplugin.dll
0x08000000 - 0x082b8000      C:\Sun\AppServer7\jdk\jre\bin\server\jvm.dll
0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
0x5dac0000 - 0x5dac8000      C:\WINDOWS\system32\rdpsnd.dll
0x76360000 - 0x76370000      C:\WINDOWS\system32\WINSTA.dll
0x5b860000 - 0x5b8b4000      C:\WINDOWS\system32\NETAPI32.dll
0x60070000 - 0x6007a000      C:\Sun\AppServer7\bin\PSAPI.DLL
0x76c90000 - 0x76cb8000      C:\WINDOWS\system32\IMAGEHLP.dll
0x10000000 - 0x10007000      C:\Sun\AppServer7\jdk\jre\bin\hpi.dll
0x77fe0000 - 0x77ff1000      C:\WINDOWS\system32\Secur32.dll
0x01400000 - 0x0140e000      C:\Sun\AppServer7\jdk\jre\bin\verify.dll
0x022b0000 - 0x022c9000      C:\Sun\AppServer7\jdk\jre\bin\java.dll
0x022d0000 - 0x022de000      C:\Sun\AppServer7\jdk\jre\bin\zip.dll
0x05c00000 - 0x05c1c000      C:\Sun\AppServer7\jdk\jre\bin\jdwp.dll
0x05c20000 - 0x05c25000      C:\Sun\AppServer7\jdk\jre\bin\dt_socket.dll
0x662b0000 - 0x66308000      C:\WINDOWS\system32\hnetcfg.dll
0x71a90000 - 0x71a98000      C:\WINDOWS\System32\wshtcpip.dll
0x07140000 - 0x0714f000      C:\Sun\AppServer7\jdk\jre\bin\net.dll
0x600b0000 - 0x600bd000      C:\Sun\AppServer7\bin\cis.dll
0x76d60000 - 0x76d79000      C:\WINDOWS\system32\iphlpapi.dll
0x76d40000 - 0x76d58000      C:\WINDOWS\system32\MPRAPI.dll
0x77cc0000 - 0x77cf2000      C:\WINDOWS\system32\ACTIVEDS.dll
0x76e10000 - 0x76e35000      C:\WINDOWS\system32\adsldpc.dll
0x76b20000 - 0x76b31000      C:\WINDOWS\system32\ATL.DLL
0x774e0000 - 0x7761d000      C:\WINDOWS\system32\ole32.dll
0x77120000 - 0x771ac000      C:\WINDOWS\system32\OLEAUT32.dll
0x76e80000 - 0x76e8e000      C:\WINDOWS\system32\rtutils.dll
0x71bf0000 - 0x71c03000      C:\WINDOWS\system32\SAMLIB.dll
0x77920000 - 0x77a13000      C:\WINDOWS\system32\SETUPAPI.dll
0x07f60000 - 0x07f66000      C:\Sun\AppServer7\jdk\jre\bin\ioser12.dll
0x07f70000 - 0x07f75000      C:\Sun\AppServer7\jdk\jre\bin\rmi.dll
0x0ffd0000 - 0x0fff8000      C:\WINDOWS\system32\rsaenh.dll
VM Arguments:
jvm_args: -DJAVA_HOME=C:/Sun/AppServer7/jdk
-Dcom.sun.aas.installRoot=C:/Sun/AppServer7
-Dcom.sun.aas.instanceRoot=C:\Sun\AppServer7\domains\domain1
-Duser.language=nl
-Duser.country=BE
-Duser.variant= exit vfprintf
-Djava.security.policy=C:/Sun/AppServer7/domains/domain1/kwatraNieuw/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer7/domains/domain1/kwatraNieuw/config/login.conf
-Djava.util.logging.manager=com.iplanet.ias.server.logging.ServerLogManager
-Dcom.sun.aas.configRoot=C:/Sun/AppServer7/config
-Dcom.sun.aas.imqLib=C:/Sun/AppServer7/imq/lib
-Dcom.sun.aas.imqBin=C:/Sun/AppServer7/imq/bin
-Dcom.sun.aas.webServicesLib=C:\Sun\AppServer7\share\lib
-XX:+AggressiveHeap -XX:+DisableExplicitGC
-Djavax.rmi.CORBA.UtilClass=com.iplanet.ias.util.orbutil.IasUtilDelegate
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl
-Dcom.sun.jdo.api.persistence.model.multipleClassLoaders=reload
-server -Xss128k -Xms512m -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=2876
-Xnoagent -Djava.compiler=NONE
java_command: <unknown>
Launcher Type: generic
Environment Variables:
CLASSPATH=C:\Program Files\QuickTime\QTSystem\QTJava.zip
PATH=C:/Sun/AppServer7/jdk\jre\bin\server;
C:/Sun/AppServer7/jdk\jre\bin;;C:/Sun/AppServer7/bin/;
C:\oracle\product\10.2.0\client_1;C:\oracle\product\10.2.0\client_1\bin;
C:\orarun\bin;C:\WINDOWS\system32;C:\WINDOWS;
C:\WINDOWS\System32\Wbem;C:\Program Files\QuickTime\QTSystem\;
C:\orarun\jdk\bin;C:\Program Files\Provision Networks\Virtual Access Client\
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 2 family 15, cmov, cx8, fxsr, mmx, sse, sse2
Memory: 4k page, physical 2088428k(641700k free), swap 4030576k(2605040k free)
vm_info: Java HotSpot(TM) Server VM (1.4.2_11-b06) for windows-x86,
built on Feb 13 2006 10:02:05 by "java_re" with MS VC++ 6.0Anyone who has more information as to what to do?
Thx.
Message was edited by:
DonStevo
Message was edited by:
DonStevo

Migration of j2ee app from Sun one App Server 6.0 to Sun one 6.5 Server

Hi all,
Currently I am involved in "J2EE" ear (webapps) migration from Sun One 6.0 to Sun One 6.5 Application Server on solaris os.Since the version and functionlity itself is major change in Sun One Server, my team had decided to build the source file and decided to port to Sun one 6.5 App Server.On doing build and compiling all source files, EJB compiler is failing on Sun one server 6.5.
Our findings on migration was as follows:
Sun one server 6.0 and its EJB compiler internally uses "kfcjdk11.jar" which is the base library to generate ejbs for "Enterprise Archive or ear file " of the application.Hence our application is suceessfully getting compiled and built on Sun one server 6.0 and running pretty fine.
However, "kfcjdk11.jar" still present in Sun One 6.5 server but its not been referred by SUN One 6.5 EJB compiler.So any successfully ear file deployed on 6.0 App Server, can be deployed on Sun One server 6.5. But to test applications/product's cycle, ear file deployed on SUN one 6.5 throws runtime errors and white screen is displayed to the user.
I had already included kfcjdk11.jar file into classpath, still its failing to compile the files.
The one of the error description is as follows:
[exec] iPlanet Enterprise Java Beans(tm) Compiler (version 6.5)
[exec]
[exec] Unexpected compilation Error:
[exec]
[exec] ejb_fac_com_server_framework_ejb_ChannelManagerBean.java:9: Superclass com.kivasoft.eb.EBHomeFactoryBase of class com.server.framework.ejb.ejb_fac_com_server_framework_ejb_ChannelManagerBean not found.
[exec] extends com.kivasoft.eb.EBHomeFactoryBase
[exec] ^
[exec] ejb_home_com_server_framework_ejb_ChannelManagerBean.java:8: Superclass com.kivasoft.eb.EBHomeBase of class com.server.framework.ejb.ejb_home_com_server_framework_ejb_ChannelManagerBean not found.
[exec] public class ejb_home_com_server_framework_ejb_ChannelManagerBean extends com.kivasoft.eb.EBHomeBase implements com.server.framework.ejb.IChannelManagerHome
[exec] ^
[exec] ejb_kcp_skel_IChannelManagerHome.java:9: Superclass com.kivasoft.ebfp.EBKCPSkelBase of class com.server.framework.ejb.ejb_kcp_skel_IChannelManagerHome not found.
[exec] extends com.kivasoft.ebfp.EBKCPSkelBase
[exec] ^
[exec] ejb_stub_IChannelManagerHome.java:9: Superclass com.kivasoft.eb.EBStubBase of class com.server.framework.ejb.ejb_stub_IChannelManagerHome not found.
[exec] extends com.kivasoft.eb.EBStubBase
[exec] ^
[exec] ejb_kcp_stub_IChannelManagerHome.java:9: Superclass com.kivasoft.ebfp.EBKCPStubBase of class com.server.framework.ejb.ejb_kcp_stub_IChannelManagerHome not found.
[exec] extends com.kivasoft.ebfp.EBKCPStubBase
[exec] ^
[exec] ejb_stub_IChannelManager.java:9: Superclass com.kivasoft.eb.EBStubBase of class com.server.framework.ejb.ejb_stub_IChannelManager not found.
[exec] extends com.kivasoft.eb.EBStubBase
[exec] ^
[exec] ejb_kcp_stub_IChannelManager.java:9: Superclass com.kivasoft.ebfp.EBKCPStubBase of class com.server.framework.ejb.ejb_kcp_stub_IChannelManager not found.
[exec] extends com.kivasoft.ebfp.EBKCPStubBase
[exec] ^
[exec] ejb_skel_com_server_framework_ejb_ChannelManagerBean.java:7: Package com.iplanet.ias.tools.monitor not found in import.
[exec] import com.iplanet.ias.tools.monitor.*;
[exec] ^
[exec] ejb_skel_com_server_framework_ejb_ChannelManagerBean.java:11: Superclass com.kivasoft.eb.EBSkelDelegate of class com.server.framework.ejb.ejb_skel_com_server_framework_ejb_ChannelManagerBean not found.
[exec] extends com.kivasoft.eb.EBSkelDelegate
[exec] ^
[exec] ejb_kcp_skel_IChannelManager.java:9: Superclass com.kivasoft.ebfp.EBKCPSkelBase of class com.server.framework.ejb.ejb_kcp_skel_IChannelManager not found.
[exec] extends com.kivasoft.ebfp.EBKCPSkelBase
[exec] ^
[exec] 10 errors
[exec]
[exec] Result: 255
Please guide us or suggest us to migrate our application to Sun one 6.5.
Thanks in advance,

Hi,
web applciation uses some of platform specific API which are not portable to App server 7.0 like uda.framework etc.
So to streamline process we are migrating applcaition to 6.5 server and also planning to rewrite whole archietecture to port it to another app server.
Thanks,

Monitoring Sun Ray Server health

I am interested in deploying Sun Ray Server as a component of a large VDI implementation. I want to be able to monitor the health of the Sun Ray Server software beyond the standard OS level stuff - number of concurrent Sun Ray Client connections for example. Is there an API (or some other mechanism) available for me to create an agent that can be monitored with standard monitoring software? Thanks!

Thanks for the info, however, I'm not looking for monitoring software - my organization already uses the IBM Tivoli suite quite successfully. I'm interested in more info on the specific Sun Ray APIs available to me to mine some health data. Thanks.

Ginga-J Sun specific API's

Similar Messages

Maybe you are looking for