Re: Resolved: Remedy JAVA api question

2008-04-03 Thread Axton
If they remove all native stuff (jni) from the java api and refactor all the
existing code (email, fb, mid-tier, etc.) with 7.5, you will be there.  It
is my understanding that the native stuff will be gone, but I've not heard
anything about refactoring the existing apps.  With mid-tier 7.1, the older
jni stuff (7.0.1) is included in the war, but who knows with the next
release.

Axton Grams

On Thu, Apr 3, 2008 at 5:30 PM, Matthew Kunkel <[EMAIL PROTECTED]>
wrote:

> ** You hit the nail on the head.  When the OS was upgraded, the JVM was
> also upgraded to 64 bit.
>
> Our infrastructure group is really pushing 64 bit, especially the
> WebSphere folks.  With everything headed in that general direction, I sure
> hope BMC starts releasing 64bit native server code.
>
> Thanks for the help!
> Matt
>
>  --
> *From:* Action Request System discussion list(ARSList) [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Axton
> *Sent:* Tuesday, April 01, 2008 8:32 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: FW: Remedy JAVA api question
>
> ** Try using a 32-bit jvm.  I am not positive on this, but loading 32-bit
> native libraries using a 64-bit jvm may be the source of your "invalid
> magic number" error.  I believe the compatiblity matrix for mid-tier, fb,
> email, etc. all state that you must use a 32-bit jvm, I assume for this
> reason.
>
> http://www.ibm.com/developerworks/java/jdk/aix/j564/sdkguide.aix64.html
>
> Axton Grams
>
> On Tue, Apr 1, 2008 at 4:01 PM, Matthew Kunkel <
> [EMAIL PROTECTED]> wrote:
>
> > ** It's a 64 bit binary.  I was thinking that the ld_library_path was
> > wrong, but it does indeed reference the directory containing the ..a's
> >
> > $ file /u/applic/wsadmin/WAS61/AppServer/java/bin/java
> > /u/applic/wsadmin/WAS61/AppServer/java/bin/java: 64-bit XCOFF executable
> > or object module not stripped
> >
> > I apologize about the confusion earlier.  For some reason I have it in
> > my head this is on another platform, but it's AIX all the way.
> >
> > Thanks,
> > Matt
> >
> >  --
> >  *From:* Action Request System discussion list(ARSList) [mailto:
> > [EMAIL PROTECTED] *On Behalf Of *Axton
> > *Sent:* Tuesday, April 01, 2008 1:04 PM
> > *To:* arslist@ARSLIST.ORG
> > *Subject:* Re: FW: Remedy JAVA api question
> >
> > ** If you run file against the java binary, what do you get back?  e.g.,
> >
> >
> >
> > [EMAIL PROTECTED] c]$ which java
> > /usr/bin/java
> > [EMAIL PROTECTED] c]$ file /usr/bin/java
> > /usr/bin/java:  ELF 32-bit MSB executable SPARC Version 1, dynamically
> > linked, stripped
> >
> > Axton Grams
> >
> > On Tue, Apr 1, 2008 at 11:29 AM, Matthew Kunkel <
> > [EMAIL PROTECTED]> wrote:
> >
> > > ** Correction:
> > >
> > > The first line should have read: "We're getting the error below when
> > > trying to use the JAVA api on an AIX platform."
> > >
> > > I originally thought it was windows, so I keep getting the process
> > > confused.  The whole app runs on a 64 bit AIX platform, no windows.
> > >
> > > Thanks,
> > > Matt
> > >
> > >  --
> > > *From:* Matthew Kunkel
> > > *Sent:* Tuesday, April 01, 2008 9:46 AM
> > > *To:* 'arslist@ARSLIST.ORG'
> > > *Subject:* Remedy JAVA api question
> > >
> > >  List,
> > >
> > > We're getting the error below when trying to use the JAVA api on a
> > > windows platform.  This particular program is running on AIX, whereas I'm
> > > most familiar with HP-UX.  I've googled the error and can't seem to find
> > > anything.  We get the same result on both the 6.3 and 7.0 versions of the
> > > API.  Any help is appreciated.
> > >
> > >
> > > Caused by: java.lang.UnsatisfiedLinkError:
> > > /u/applic/Remedy/libarjni70.a (0509-022 Cannot load module
> > > /u/applic/Remedy/libarjni70.a.
> > > 0509-103 The module has an invalid magic number.)
> > > at
> > > com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
> > > at
> > > com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
> > > at
> > > com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
> > > at
> > > com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
> > > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
> > > at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
> > > at
> > > com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
> > > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
> > > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
> > >
> > >
> > > Thanks,
> > > Matt
> > >
> > > --
> > >
> > > ***
> > > This email and any files transmitted with it are confidential and intended
> > > solely for the individual or entity to whom they are addressed. If you 
> > > 

Resolved: Remedy JAVA api question

2008-04-03 Thread Matthew Kunkel
You hit the nail on the head.  When the OS was upgraded, the JVM was
also upgraded to 64 bit.  
 
Our infrastructure group is really pushing 64 bit, especially the
WebSphere folks.  With everything headed in that general direction, I
sure hope BMC starts releasing 64bit native server code.
 
Thanks for the help!
Matt



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Tuesday, April 01, 2008 8:32 PM
To: arslist@ARSLIST.ORG
Subject: Re: FW: Remedy JAVA api question


** Try using a 32-bit jvm.  I am not positive on this, but loading
32-bit native libraries using a 64-bit jvm may be the source of your
"invalid magic number" error.  I believe the compatiblity matrix for
mid-tier, fb, email, etc. all state that you must use a 32-bit jvm, I
assume for this reason.

http://www.ibm.com/developerworks/java/jdk/aix/j564/sdkguide.aix64.html

Axton Grams


On Tue, Apr 1, 2008 at 4:01 PM, Matthew Kunkel
<[EMAIL PROTECTED]> wrote:


** 
It's a 64 bit binary.  I was thinking that the ld_library_path
was wrong, but it does indeed reference the directory containing the
..a's
 
$ file /u/applic/wsadmin/WAS61/AppServer/java/bin/java
/u/applic/wsadmin/WAS61/AppServer/java/bin/java: 64-bit XCOFF
executable or object module not stripped
 
I apologize about the confusion earlier.  For some reason I have
it in my head this is on another platform, but it's AIX all the way.
 
Thanks,
Matt




From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton

Sent: Tuesday, April 01, 2008 1:04 PM
To: arslist@ARSLIST.ORG
Subject: Re: FW: Remedy JAVA api question


** If you run file against the java binary, what do you get
back?  e.g., 


[EMAIL PROTECTED] c]$ which java
/usr/bin/java
[EMAIL PROTECTED] c]$ file /usr/bin/java
/usr/bin/java:  ELF 32-bit MSB executable SPARC Version 1,
dynamically linked, stripped

Axton Grams


On Tue, Apr 1, 2008 at 11:29 AM, Matthew Kunkel
<[EMAIL PROTECTED]> wrote:


** 
Correction:
 
The first line should have read: "We're getting the
error below when trying to use the JAVA api on an AIX platform."
 
I originally thought it was windows, so I keep getting
the process confused.  The whole app runs on a 64 bit AIX platform, no
windows.
 
Thanks,
Matt



From: Matthew Kunkel 
Sent: Tuesday, April 01, 2008 9:46 AM
To: 'arslist@ARSLIST.ORG'
Subject: Remedy JAVA api question


List,
 
We're getting the error below when trying to use the
JAVA api on a windows platform.  This particular program is running on
AIX, whereas I'm most familiar with HP-UX.  I've googled the error and
can't seem to find anything.  We get the same result on both the 6.3 and
7.0 versions of the API.  Any help is appreciated.
 
 
Caused by: java.lang.UnsatisfiedLinkError:
/u/applic/Remedy/libarjni70.a (0509-022 Cannot load module
/u/applic/Remedy/libarjni70.a.
0509-103 The module has an invalid magic number.)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(Ne
wConnectionInitialReadCallback.java:113)
at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(Ai
oReadCompletionListener.java:165)
at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.
java:217)
at
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFu
ture.java:161)
at
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java
:743)
at
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
 
 
Thanks,
Matt






**
This email and any files transmitted with it are confidential and
intended solely for the individual or entity to whom they are addressed.
If you have received this email in error destroy it immediately.
**
Wal-Mart Confidential