headers
Jürgen Rohrbach | 3 Sep 2009 07:13
Picon
Favicon

Re: WebObjects-admin Digest, Vol 43, Issue 1

hello,

did you try the compiler switches:

-target 1.5
-source 1.5

when you compile with 1.6 and want's to depoly on 1.5?

juergen

Am 02.09.2009 um 21:00 schrieb webobjects-admin-request <at> omnigroup.com:

> Send WebObjects-admin mailing list submissions to
> 	webobjects-admin <at> omnigroup.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.omnigroup.com/mailman/listinfo/webobjects-admin
> or, via email, send a message with subject or body 'help' to
> 	webobjects-admin-request <at> omnigroup.com
>
> You can reach the person managing the list at
> 	webobjects-admin-owner <at> omnigroup.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebObjects-admin digest..."
>
>
> Today's Topics:
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Brendan Duddridge | 1 Sep 2009 20:31
Favicon

Run your WO apps on Leopard Server (Intel) with Java 6

Hey WO Folks,

So I had a class version mismatch exception when building from Snow  
Leopard (JDK 1.6) and deploying on Leopard Server (JDK 1.5). So I  
wanted to switch my servers to use JDK 1.6 by default. Nothing we  
tried would make that happen. We tried dragging the Java 6 entry in  
Java Preferences up to the top of the list and rebooting the Xserve,  
but that still didn't work. We also tried changing the CurrentJDK to  
point to the 1.6.0 directory. But that also didn't work. Tried  
changing the Current symlink to point to 1.6.0 instead of to A as is  
by default.

Well, when I say it didn't work, I mean it didn't help to launch our  
WO apps with Java 1.6. They still launched with Java 1.5, even though  
typing 'java -version' into the command line returned 1.6, typing in  
'sudo -u appserver java -version' returned 1.5.

So the solution was to modify the build.xml file in Eclipse to have it  
generate a hard coded path to the JVM to point to 1.6.

Here's what I added to the build.xml file's <woapplication> task:

JVM="/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/ 
bin/java"

So it looks like this now:

<woapplication name="${build.app.name}" JVM="/System/Library/ 
Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/java" destDir="$ 
{dest.dir}" customInfoPListContent="${customInfoPListContent}"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vicky C. Miller | 12 Jun 2009 21:50

(no subject)


Regards,

Vicky C. Miller

Consulting, Services and Solutions Group, Inc.

9926 Main Street

Fairfax, Virginia 22031-3419

Telephone: (703)385-2008, Ext. 225

Facsimile: (703)385-2063

Website: www.cssg.com
"Accountability Software Is Our Focus"R
Permalink | Reply | 1 comment |
headers
Vicky C. Miller | 22 May 2009 21:42

WebObjects 5.2.4, Solaris 9, Apache 2.0.x or 2.2.x?

Hello:

We are currently running WebObjects 5.2.4, Solaris 9, and Apache 1.3.  Is
there a WebObjects Apache module for Apache 2.0.x or 2.2.x that is
compatible with WebObjects 5.2.4 and Solaris 9?  Thanks in advance.
Permalink | Reply | 0 comments |
headers
Tanmoy | 31 Mar 2009 19:54
Picon
Favicon

Re: oracle constraint problem, sequences for generating unique IDs

Hi Vicky,

WO provides a very simple way to implement this. Just create a  
sequence with the name <TABLENAME>_SEQ.
And then you dont have to worry about anything. WO will take care of  
incrementing this sequence every-time you insert a record automatically.

You don't have to incorporate this column during your insert. (Setting  
the EOs for insert)

E.g. your table name : emp_sal . Sequence name will be emp_sal_seq.

Thanks,
Tanmoy

On 31-Mar-09, at 7:11 AM, Vicky C. Miller wrote:
>
>> Hello:
>>
>>
>>
>> We are attempting to overcome an oracle constraint problem,  
>> specifically:
>>
>>
>>
>> Caused by: java.sql.BatchUpdateException: ORA-00001: unique  
>> constraint
>> (..SYS_C001711) violated
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vicky C. Miller | 31 Mar 2009 16:11

oracle constraint problem, sequences for generating unique IDs

Hello:

We are attempting to overcome an oracle constraint problem, specifically:

Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint
(..SYS_C001711) violated

We've resolved the error with a short term solution but we are trying to get
away from sequences for generating unique IDs since it is expensive on the
performance side.  Has anyone implemented WO such that the capability to
cache sequence numbers is functional and it is NOT necessary to cache and
query for the next sequence number before making an update to Oracle?

Thanks in advance.
Permalink | Reply | 1 comment |
headers
Vicky C. Miller | 30 Mar 2009 01:02

Error: com.webobjects.foundation.NSForwardException

Hello:

Is anyone familiar with this error, the typical cause(s) and resolution?

Vicky

Application:

/WebObjects -
http://.../cgi-bin/WebObjects/solaradmin.woa/24/wo/g1FIdrdEzXGPtzLx7SOHtM/2.
3

Error:

com.webobjects.foundation.NSForwardException

Reason:

com.webobjects.foundation.NSForwardException

  _____  

StackTrace:

com.webobjects.foundation.NSForwardException for
com.webobjects.jdbcadaptor.JDBCAdaptorException: Io exception: The Network
Adapter could not establish the connection
at com.webobjects.jdbcadaptor.JDBCContext.connect(JDBCContext.java:244)
at com.webobjects.jdbcadaptor.JDBCContext._tryConnect(JDBCContext.java:331)
at
(Continue reading)

Permalink | Reply | 2 comments |
headers
Vicky C. Miller | 23 Feb 2009 18:21

Solaris 9 / Oracle 10 G / WebObjects 5.2.4

Is anyone running Solaris 9 / Oracle 10 G / WebObjects 5.2.4?  If so, how
long have you had it running and have there been any issues?

We're currently running Solaris 8 / Oracle 9 / WebObjects 5.2.4.  Are there
any gotchas upgrading to Solaris 9 or Oracle 10 G?  When we upgrade Solaris
and Oracle, is there anything that has to be done with the WebObjects 5.2.4
- like reinstalled?
Permalink | Reply | 0 comments |
headers
Vicky C. Miller | 10 Feb 2009 03:10

WebObjects 5.2.4 on Solaris 9?

Is anyone running WebObjects 5.2.4 on Solaris 9?
Permalink | Reply | 3 comments |
headers
ingob1 | 7 Nov 2007 10:40
Picon

Session Timeout on wrong instance

Hi,

we have got a problem for some months now that we can’t find a solution for. 

The situation: We have an application that is running on four different application servers (with quite
some instances on each server, servers running on linux) controlled by monitors running on two of those
servers (each monitor is responsible for 2 servers). The wotaskd is running on each server as well.
Finally we got two web servers (Apache 2.0.49). We use Java 1.4.2, WebObjects 5.2.3.

The problem: Several times a day on each of the instances we got session timeouts
(SessionRestorationErrors). But the sessions don’t time out, the requests are placed on the wrong
instances. Of course, the session ids are not known on those wrong instances so the
SessionRestorationErrors take place. 
What we have done so far: we tried setting send timeout, receive timeout and connect timeout in “Load
Balancing and Adaptor Settings” to values of one minute and above without any success. We are logging
the woadaptor now. It seems we have got some kind of connection trouble:

Error: couldn't connect to 10.0.0.40 (1085): Operation now in progress
Error: Error connecting to server 10.0.0.40
Warn: Unable to find instance 55. Attempting to select another.
Warn: Unable to find instance 55. Attempting to select another.
Warn: Unable to find instance 60. Attempting to select another.

But 10.0.0.40:1085 is up and running. This error message is just been thrown about every 10 or 20 minutes and
not all the time. 
We found some similar problems in mailing lists but none was helpful so far. Any suggestions how we can get
rid of this problem? Thanks in advance.

Ingo
--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Webobjects Developer | 15 Oct 2007 08:11
Picon

Installing new application

If I have a running server, what is the suggested way of updating an
application on the server?
Here is my current technique (below). I run one instance at once and this
technique works consistently for me, but requires me to shut down the web
server.

It seems like if I skip any of the steps, webobjects keeps using some cached
version of the old application. The sequence of steps (below) works, but it
is tedious and has more downtime than I'd prefer.

Is there an easier way to do this?

Installing new webobjects application.

- Using monitor, stop my instance(s) from running.

- Using server admin, turn off monitor, save.

- Using server admin, stop webobjects.

- Using server admin, stop web.

- Now replace the application and update databases.

- Using server admin, start web.

- Using server admin, start webobjects.

- Using server admin, turn on monitor, save.
(Continue reading)

Permalink | Reply | 3 comments |

Gmane