× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



"Also, do you maintain a connection to your production WAS server within
WDSC? If you do that may be causing the problem. I ended up removing the
production server from my WDSC interface. In my case every time I would
make a little change on the test server it would deploy the code to the
production server."

Interesting ... this may be the root of my problem.



Royce Stearns




Faizulla Khan <fkhan@xxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/27/2007 08:26 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Webfaced app failing to init on local WAS 6.1







I look for the .ear file in the entire WDSC directory structure to see how
many instances there are. It ends up in several places. One thing you can
do is go through Admin console and try to remove the file from there. This
usually works.

Also, do you maintain a connection to your production WAS server within
WDSC? If you do that may be causing the problem. I ended up removing the
production server from my WDSC interface. In my case every time I would
make a little change on the test server it would deploy the code to the
production server.


Faizulla Khan
Information Services
Grand Circle Travels
617-346-6058




rstearns@managein
c.com
Sent by: To

wdsci-l-bounces@m Websphere Development Studio Client

idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx>
cc


06/27/2007 02:56 Subject

PM Re: [WDSCI-L] Webfaced app failing
to init on local WAS 6.1

Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>






"an incomplete uninstall of a previous application"
That's what I first suspected...
Here's the steps I used to uninstall:

remove it from the server.
Start and stop the server
Delete the application from webfacing perspective including removing it
from the workspace
Delete the EAR from the java perspective including removing it from the
workspace
Re start WDSC
And I've even deleted the local 6.1 server and created a new one.


I'm now reinstalling WDSC to see if I can re web face the application.

Is there a easier method to insure the application is uninstalled from the
server?

thanks,
Royce Stearns





Faizulla Khan <fkhan@xxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/27/2007 11:08 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Webfaced app failing to init on local WAS 6.1








I remember this having to do with an incomplete uninstall of a previous
application. Completely uninstal your previous app from the server. Reboot
and then webface again.

Hope this helps
Faizulla Khan
Information Services
Grand Circle Travels
617-346-6058




rstearns@managein
c.com
Sent by: To

wdsci-l-bounces@m Websphere Development Studio Client

idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx>
cc


06/27/2007 01:15 Subject

PM [WDSCI-L] Webfaced app failing to
init on local WAS 6.1

Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>






This is really strange.
I've webfaced an app and had it running on both a WAS 6.1 i5 and my local
WDSC WAS 6.1. This was the first app I deployed on my new WDSCi 7.0
installation. (I'm tempted to reinstall WDSCi)

I removed it from the local server and tried to re deploy it and it
failed. Thinking I had broken the app prior to re deploying I webfaced
the app again and deployed it again to the local server and it continued
to fail. I added some test JSP's to the server and they run just fine.
The webfaced app is called AM4. Nothing has changed on the app that I'm
webfacing.
The error is consistent after re webfacing and trying to deploy it ...
consistently I get the error:

[6/27/07 9:48:56:484 PDT] 00000012 ServletWrappe E SRVE0100E: Did not
realize init() exception thrown by servlet action:
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:195)

Is this a server error or an app error?

More Details:

[6/27/07 9:48:53:843 PDT] 00000012 WebGroup A SRVE0169I: Loading
Web Module: AM4.
[6/27/07 9:48:54:687 PDT] 00000012 PropertyMessa I
org.apache.struts.util.PropertyMessageResources <init> Initializing,
config='org.apache.struts.util.LocalStrings', returnNull=true
[6/27/07 9:48:54:734 PDT] 00000012 PropertyMessa I
org.apache.struts.util.PropertyMessageResources <init> Initializing,
config='org.apache.struts.action.ActionResources', returnNull=true
[6/27/07 9:48:55:515 PDT] 00000012 PropertyMessa I
org.apache.struts.util.PropertyMessageResources <init> Initializing,
config='com.ibm.as400ad.webfacing.runtime.rtmessage', returnNull=true
[6/27/07 9:48:55:640 PDT] 00000012 PropertyMessa I
org.apache.commons.logging.impl.Jdk14Logger info Initializing,
config='com.ibm.as400ad.webfacing.runtime.rtmessage', returnNull=true
[6/27/07 9:48:55:718 PDT] 00000012 PropertyMessa I
org.apache.commons.logging.impl.Jdk14Logger info Initializing,
config='com.ibm.as400ad.webfacing.runtime.rtmessage', returnNull=true
[6/27/07 9:48:55:828 PDT] 00000012 ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened
incident stream file C:\Program
Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_77807780_07.06.27

_09.48.55_0.txt
[6/27/07 9:48:56:453 PDT] 00000012 ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC
closed incident stream file C:\Program
Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_77807780_07.06.27

_09.48.55_0.txt
[6/27/07 9:48:56:484 PDT] 00000012 ServletWrappe E SRVE0100E: Did not
realize init() exception thrown by servlet action:
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
at
com.ibm.as400ad.webfacing.runtime.httpcontroller.HttpSessionManager.<clinit>(


HttpSessionManager.java:42)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
at
com.ibm.as400ad.webfacing.runtime.controller.struts.WFPlugIn.init(
WFPlugIn.java:43)
at org.apache.struts.action.ActionServlet.initModulePlugIns(
ActionServlet.java:1158)
at org.apache.struts.action.ActionServlet.init(
ActionServlet.java:486)


Royce Stearns

--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.