When will WLS 8.1 SP2 be GA ?

Hi BEA,
When will SP2 for WLS 8.1 be GA ?
I see some fixes i need on the release notes but
SP2 is not available for download.
Thanks
Yshemi

I bought my Icon just a few days over 2 months ago expecting it to ship with 8.1. I can not communicate how disappointed I am in VZ for NOT sending the 8.1 update out. I have used Apple and Android, each have their own following but to do this to paying customers is not right. I work for a software company that relys heavily on Microsoft products and we would NEVER do this to a customer. If it was not for the fact that I had terrible coverage from AT&T I would look at switching to another carrier but VZ is about the only reliable one where I live.
But this latest trick is more than disheartening, it should approach being illegal. And I had the same experience when asking about the Icon in a VZ store before buying it. The salesperson didn't want to talk Windows Phone anything and kept pushing Galaxy and iPhone. That is why I ordered mine online, because of their sales rep.
Not a good move VZ to keep customers happy!

Similar Messages

When will wls try to garbage collect ?

The docs for the option "Low memory GC threshold" say that this is the "Threshold
level at which WLS will try to garbage collect once the granularity report has
been met".
My question is: When is this condition met ? If at least once there has been a
granularity report in the log ? Or if the server has been set to Warning state
The problem Im trying to address is that my "Low memory GC threshold" is set to
20% and my server has reached only 1% free memory and garbage collection did not
run, I had to force it via console.
Thanks in advance, Giselle

I am wonder when the WLS activate or passivate session and how can I          control it?
          > From documents, sessionWillPassivate in HttpSessionActivationListener will
          be
          > executed when a session is about to passivate on one server (ie. WLS
          instance)
          > and the sessionDidActivate method when the same session has been activated
          on
          > a second server.
          >
          > But I have monitor the behavior for a long time by setting
          PersistentStoreType
          > to file, memory, replicated. sessionDidActivate and sessionWillPassivate
          will
          > never executed. I expected it will passivate and activate when session is
          replicated
          > between servers or persist in files. Any ideas?
          What version of WL? the interface you describe was new in Servlet 2.3, so it
          may not be implemented until 6.1 or even 7.x.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Karen Law" <[email protected]> wrote in message
          news:3ec86188$[email protected]..
          >

WLS 8.1 SP2 Availability

When will WLS 8.1 SP2 be available?
Thanks.

WLS 8.1 SP2 supports JDK 1.4.1_02
Teresa Blunt <[email protected]> wrote:
Is WLS 8.1 SP2 support with JDK 1.4.2?

Difference between WLS 6.1 SP2 and SP3

I have recently tested my application in WLS 6.1 SP3 (who work normally in WLS
6.1 SP2) , I have problem with my jsp page for merging a jsp in another
What need I do to correct it ?

Steven,
The CGIServlet for WebLogic will not run a CGI that doesn't have an extension.
Just add and extension to your executable and it should run fine.
jeff
"Steven" <[email protected]> wrote:
Hi all,
I am currently facing a problem with CGI binaries via CGIServlet on WLS
6.1
sp4. The web.xml file has been configured correctly as follows:
-------- start of web.xml -----------
<servlet>
<servlet-name>CGIServlet</servlet-name>
<servlet-class>weblogic.servlet.CGIServlet</servlet-class>
<init-param>
<param-name>cgiDir</param-name>
<param-value>/web/bea6.1sp2/wlserver6.1/config/ngwapp/applications/NGWWebApp
/cgi-bin</param-value>
</init-param>
<init-param>
<param-name>*.pl</param-name>
<param-value>/web/perl5/bin/perl5.00405</param-value>
</init-param>
<init-param>
<param-name>*.cgi</param-name>
<param-value>/web/perl5/bin/perl5.00405</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>CGIServlet</servlet-name>
<url-pattern>/cgi-bin/*</url-pattern>
</servlet-mapping>-------- end of web.xml ---------
When a call is made to http://.../cgi-bin/dialogserver , this results
in a
404-File Not Found error.
The contents of the cgi-bin directory have not been altered and I did
not
face this problem earlier when I was using sp2.
It only happened after I upgraded to sp4. Can anyone help?
best rgds,
steven.

ERROR: Error from ejbc: in WLS 6.1 sp2 Win2K

Never had this problem before. Started new project using WLS 6.1 sp2 under Windows
2K Prof., using ANT & get;
ERROR: Error from ejbc:
In EJB NOTiFYEJB, method createUser defined in the remote interface either does
not exist in the bean class, or it is not a public method. Each method in the
remote interface must have a corresponding public method in the bean class.
BUILD FAILED
I saw a posting which referred to a problem with Win2K & an old (1.2) JDK in the
path. I have put C:\bea\jdk131 at the front of my class path but still get this
error.

The problem was nothing to do with classpaths etc.
CMP does not support "Date" types and in my EJB I had Date types, I changed these
to "long" and converted all Dates to number of milleseconds from 1970 and persisted
them to a number column in Oracle.
It was the entries in the weblogic-cmp-rdbms.xml which was the root of the problem.
"Roger Lee" <[email protected]> wrote:
>
Matthew,
Thanks for yor suggestions.
My classpath is set in the ANT.BAT & only points to the tools.jar, weblogic_sp.jar
& weblogic.jar.
I have my JARs in a manfest file in each directory with the "Class-Path:"
entry.
I have also added a new Bean with compiles & ejbcs fine. But I still
get an error
with my "createUser" method, saying the interface does not exist in the
bean class
or is not a public method.
I have even changed it's name to "createUserCandidate" just in case it
was clashing
with an existing method.
Any other ideas for investigation?
Thanks.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Roger Lee wrote:
The "warnings saying classes are being loaded from your classpath"are, I believe
just warning from Ant. I searched the newsgroups and it appears thatthis is not
a problem.These warnings are from ejbc. They are there to let you know that classes\interfaces
needed by your EJB are being loaded from your classpath and not your
jar. They
should be taken seriously. This could definitely be the cause of your
problem. As I
said in my previous posting, ejbc could be loading an old version of
your bean class
from your classpath. This old class may not contain the createUsermethod
with the
same signature as the method in your remote interface.
Is this an issue with WLS 6.1 sp2?I don't believe so.
I've wasted so much time on this any help would be appreciated.You essentially have three options.
1. Take my advice and make sure your classes are being loaded fromyour
jar and not
the classpath.
2. Post your entire jar so we can try to reproduce the problem.
3. Contact support.
- Matt
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Your bean and interface look fine. One thing you might try is explicitly
declaring
your createUser method to be public in your remote interface. I
don't
think this
will change the outcome but it's worth a try. When you run ejbcdo
you
get any
warnings saying classes are being loaded from your classpath ratherthan
your jar?
If this were the case, you could have an old copy of your bean inyour
classpath
that ejbc is picking up. If this doesn't help, I think the next
step
is to send me
or post your entire jar.
- Matt
Roger Lee wrote:
Typo that should have been "path", I had added "C:\bea\jdk131"
to
the
front of
my path & was getting the error.
Enclose my two classes in the attached file.
Thanks for you help.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Make sure you put C:\bea\jdk131 in front of your path (not classpath).
:) Assuming
this isn't the problem, can you please post any createUser method
declarations
in your
remote interface and the corresponding createUser methods in yourbean
class?
- Matt
Name: NOTiFY_&_NOTiFYBean.java
NOTiFY_&_NOTiFYBean.java Type: java/*
Encoding: base64

Upgrading WLS 8.1 SP2 to SP5: does SSL setup need to be re-done?

All,
Our production application has been built using Workshop 8.1 SP2, and is deployed on a WLS 8.1 SP2. We are now wanting to upgrade to SP5, and so I used the "Smart Update" utility to upgrade my local instance to SP5. Our application is accessed over SSL, so I was wondering if the whole SSL-setup that was done when we setup our production SP2 environment a year ago needs to be re-done? Our application has a web module, two java projects, uses SSL-based web-services and has a custom Oracle JAAS login module. I already found out that there is a particular setting on the domain that has changed between SP2 and SP5 that allows anonymous lookup of MBeans(Anonymous Admin Lookup Enabled). Are there any other such settings/considerations i need to be aware of in moving from SP2 to SP5?
All help is appreciated..it will help me decide on moving to SP5.
Thanks in advance!
Vik.

Hi Vik
When you use smartupdate to upgrade from sp2 to sp5, it will upgrade only the weblogic workshop instance and not the domains.
Either you will have to upgrade the existing sp2 domain to sp5 or create a new sp5 domain and configure it just like sp2.
After the upgrade open the config.xml under the new domain and check the SSL config under the server just to make sure.As far as the SSL config is concerned it did not change from sp2 to sp5.
More information on this is available at
http://e-docs.bea.com/platform/docs81/upgrade/faq.html
Thanks
Vimala

Problem starting wls 6.1 sp2

Hi
I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
to Solaris 8.
I have modified my windows statup scripts to Solaris, but I get a strange error
when starting weblogic. I am starting the server as root and my weblogic.policy
file is modified according to my installation.
Has anybody encountered anything similar?
<Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
management web application - <all-internal-apps>. Managed servers may be unable
to start.
java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
My startup script is as follows
bash-2.03$ more startWeblogic.sh
#!/usr/bin/bash
# Set user-defined variables.
export PROJECT=postdanmark
export ENVIRONMENT=test
export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
echo off
echo *********************************************
echo * Starting weblogic application server *
echo *********************************************
# Set WLS_PW equal to your system password for no password prompt server startup.
export WLS_PW=certifikat
# Set Production Mode. When set to true, the server starts up in production mode.
When set to false, the server starts up i
n development mode. The default is false.
export STARTMODE=false
export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
ties/logging.properties"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
_8"
export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
echo on
echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
"$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server

Hi.
Try placing the wl_management_internal2.war file from the mydomain/.wlstaging directory into the directory your server is expecting.
Regards,
Michael
Peter Buus wrote:
Hi
I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
to Solaris 8.
I have modified my windows statup scripts to Solaris, but I get a strange error
when starting weblogic. I am starting the server as root and my weblogic.policy
file is modified according to my installation.
Has anybody encountered anything similar?
<Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
management web application - <all-internal-apps>. Managed servers may be unable
to start.
java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
My startup script is as follows
bash-2.03$ more startWeblogic.sh
#!/usr/bin/bash
# Set user-defined variables.
export PROJECT=postdanmark
export ENVIRONMENT=test
export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
echo off
echo *********************************************
echo * Starting weblogic application server *
echo *********************************************
# Set WLS_PW equal to your system password for no password prompt server startup.
export WLS_PW=certifikat
# Set Production Mode. When set to true, the server starts up in production mode.
When set to false, the server starts up i
n development mode. The default is false.
export STARTMODE=false
export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
ties/logging.properties"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
_8"
export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
echo on
echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
"$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server--
Michael Young
Developer Relations Engineer
BEA Support

When will Best Buy offer Vista Service Pack 2?

It looks like all the Vista PC's on bestbuy.com have service pack 1. Microsoft released Service Pack 2 on May 26. When will Best Buy PC's come with Vista Service Pack 2 installed? It is hard for a person to upgrade to SP2l themsevles?

When you purchase your computer from best buy with optimization service (or for an existing PC) the update to SP2 is done during The optimization. At least at my precinct we do.
J
Any advice given on this forum is strictly measured against your ability to interpret that advice and in no way reflects the opinions, legality, policies or opinions of myself nor that of Best Buy.
When all Plausible explanations have been eliminated the the only explanation that remains no matter how ridiculous is the truth
Just Because You Think your an IT Professional doesn't mean you are one..... and Check your spelling.
Its Nice to be Somebody's Hero

WLS 7.0 sp2 - Servlet Problems with SOAP messages

          I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
          XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
          support of JAXM? The System.out.println's indicate I have successfully received
          the incoming SOAP request and then successfully formatted the SOAP response, but
          upon returning saving the response it appears to blow up. Does anyone have any
          suggestions?
          I need to do the following in a servlet:
          - receive an incoming SOAP request with an embedded XML message
          - perform some processing
          - return a SOAP response with an embedded XML message
          Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
          <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
          7,name=isd.war,context-path=)] Root cause of ServletException
          java.lang.Error: NYI
          at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
          eImpl.java:360)
          at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
          (ServletStubImpl.java:1058)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:401)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:306)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
          n.run(WebAppServletContext.java:5445)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
          eManager.java:780)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
          rvletContext.java:3105)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
          pl.java:2588)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          I've stripped the code down so that all it does is verifies the incoming SOAP/XML
          request and creates a hard-coded response... be gentle... I'm a novice at this
          import javax.xml.soap.*;
          import javax.servlet.*;
          import javax.servlet.http.*;
          // import javax.xml.transform.*;
          import java.util.*;
          import java.io.*;
          public class RegisterServlet extends HttpServlet
          static MessageFactory fac = null;
          static
          try
          fac = MessageFactory.newInstance();
          catch (Exception ex)
          ex.printStackTrace();
          public void init(ServletConfig servletConfig) throws ServletException
          super.init(servletConfig);
          public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
          IOException
          try
          System.out.println("** Note: doPost() Entering req = " + req);
          // Get all the headers from the HTTP request
          MimeHeaders headers = getHeaders(req);
          // Get the body of the HTTP request
          InputStream is = req.getInputStream();
          // Now internalize the contents of a HTTP request
          // and create a SOAPMessage
          SOAPMessage msg = fac.createMessage(headers, is);
          System.out.println("** Note: doPost() Step A");
          SOAPMessage reply = null;
          reply = onMessage(msg);
          System.out.println("** Note: doPost() Step B reply = " + reply);
          if (reply != null)
          * Need to call saveChanges because we're
          * going to use the MimeHeaders to set HTTP
          * response information. These MimeHeaders
          * are generated as part of the save.
          if (reply.saveRequired())
          System.out.println("** Note: doPost() Step C reply.saveRequired()");
          reply.saveChanges();
          resp.setStatus(HttpServletResponse.SC_OK);
          putHeaders(reply.getMimeHeaders(), resp);
          // Write out the message on the response stream
          OutputStream os = resp.getOutputStream();
          System.out.println("** Note: doPost() Step D os = " + os);
          reply.writeTo(os);
          os.flush();
          else
          resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
          catch (Exception ex)
          throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
          static MimeHeaders getHeaders(HttpServletRequest req)
          Enumeration enum = req.getHeaderNames();
          MimeHeaders headers = new MimeHeaders();
          while (enum.hasMoreElements())
          String headerName = (String)enum.nextElement();
          String headerValue = req.getHeader(headerName);
          StringTokenizer values =
          new StringTokenizer(headerValue, ",");
          while (values.hasMoreTokens())
          headers.addHeader(headerName,
          values.nextToken().trim());
          return headers;
          static void putHeaders(MimeHeaders headers, HttpServletResponse res)
          Iterator it = headers.getAllHeaders();
          while (it.hasNext())
          MimeHeader header = (MimeHeader)it.next();
          String[] values = headers.getHeader(header.getName());
          if (values.length == 1)
          res.setHeader(header.getName(),
          header.getValue());
          else
          StringBuffer concat = new StringBuffer();
          int i = 0;
          while (i < values.length)
          if (i != 0)
          concat.append(',');
          concat.append(values[i++]);
          res.setHeader(header.getName(), concat.toString());
          // This is the application code for handling the message.
          public SOAPMessage onMessage(SOAPMessage message)
          SOAPMessage replymsg = null;
          try
          System.out.println("** Note: OnMessage() Entering msg = " + message);
          //Extract the ComputerPart element from request message and add to reply SOAP
          message.
          SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
          SOAPBody reqsb = reqse.getBody();
          //System.out.println("** Note: OnMessage() Step B");
          System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
          + reqsb);
          //Create a reply mesage from the msgFactory of JAXMServlet
          System.out.println("** Note: OnMessage () Step B");
          replymsg = fac.createMessage();
          SOAPPart sp = replymsg.getSOAPPart();
          SOAPEnvelope se = sp.getEnvelope();
          SOAPBody sb = se.getBody();
          System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
          = " + sb);
          se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
          System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
          = " + sb);
          replymsg.saveChanges();
          System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
          catch (Exception ex)
          ex.printStackTrace();
          return replymsg;


Michael,
I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
After digging into the WLS code and FOP(old version). i found the conflict happens
on
the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
following when startup weblogic server:
System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
But the FOP code try to use the "org.xml.sax.parser" system property to find the
sax parser then conlict happens.
Here is the response from BEA support :
"I consulted with our developers regarding the question of whether we can change
the hard-coded value for the java system property: org.xml.sax.parser by using
a configuration parameter and I found that unfortunately there is no specific
setting to change the value. As you had mentioned in your note the org.xml.sax.parser
system property can be changed programmatically in your application code."
I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
any more) and XML Registy for WLS8.1.
Good luck.
David Liu
Point2 Technologies Inc.
"p_michael" <[email protected]> wrote:
>
Help.
When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
with XML
parsing that did not previously exist.
We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
What does this mean? And, what should we do about it.
p_michael

Iplanet 6.x, NSAP & WLS 6.1 SP2

This is very strange. I can get NSAPI with iplanet 4.x to come up fine (everything proxies, etc. as it should). When we try to get iPlane 6.x working with NSAPI and WLS 6.1 SP2...nothing..doesn't work. We're running everything on Solaris.
Does anyone have or know of some good documentation that might describe how to get NSAPI working between WLS 6.1 and iPlanet 6...all the examples I've been seeing are mostly Windows paths, .dlls', etc. I'd love to see some working magnus.conf & obj.conf, etc. using WLS6.1 SP2 and iPlanet 6...we're not clustered and we're not using SSL (yet) so it's pretty vanilla.
What's blowing my mind is why iplanet 4.x works and 6.x doesn;t?? I wonder if the differences between the two are really that great. I checked BEA's doc...and like I said...it seemed a bit cryptic...someone told me ther was a typo or two regarding what was to go in magnus or was it obj.conf...I don't recall..it's just frustrating trying to get NSAPI up and running with WLS 6.1 SP2 and iPlanet 6. Any ideas? Thanks!!

Thanks Kumar. Does the syntax change (such as WebLogicCluster=xxxxxxxxxxxxxxx) if
we are running a single instance of WebLogic (a non-clustered environment)?
Thanks,
Doug
Kumar Allamraju <[email protected]> wrote:
In iplanet 6.x
magnus.conf should have
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib=/usr/local/netscape/plugins/libproxy.so
Init fn="wl_init"
and obj.conf should have
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy \
WebLogicCluster="myweblogic.com:7001,yourweblogic.com:7001,\
theirweblogic.com:7001" PathTrim="/weblogic"
</Object>
Pls post the exact errors that you are seeing, so that we can help
Kumar
"Doug E." wrote:
This is very strange. I can get NSAPI with iplanet 4.x to come up fine(everything proxies, etc. as it should). When we try to get iPlane 6.x
working with NSAPI and WLS 6.1 SP2...nothing..doesn't work. We're running
everything on Solaris.
Does anyone have or know of some good documentation that might describehow to get NSAPI working between WLS 6.1 and iPlanet 6...all the examples
I've been seeing are mostly Windows paths, .dlls', etc. I'd love to see
some working magnus.conf & obj.conf, etc. using WLS6.1 SP2 and iPlanet
6...we're not clustered and we're not using SSL (yet) so it's pretty vanilla.
What's blowing my mind is why iplanet 4.x works and 6.x doesn;t?? I wonderif the differences between the two are really that great. I checked BEA's
doc...and like I said...it seemed a bit cryptic...someone told me ther
was a typo or two regarding what was to go in magnus or was it obj.conf...I
don't recall..it's just frustrating trying to get NSAPI up and running
with WLS 6.1 SP2 and iPlanet 6. Any ideas? Thanks!!

IIS Plug for WLS 6.1 SP2: The specified procedure could not be found.

I get an the following error message "The specified procedure could not be
found." in my browser when trying to use the IIS-proxy plugin on WLS 6.1 sp2
Windows 2000
Has anyone else encountered this message? Any solutions?
Regards,
Jonas Klemming

Thank you for posting your answer, and then solution! :> I was fighting
with my IIS/WLS installation last night when I was about to give up, I came
across your posting. Although I'm playing with 7, I thought I would try
reading your posting anyways, and thankfully I did. What I saw, reminded me
to look at the steps one more time and I found I wasn't forwarding the
.wlforward piece on! So thank you veyr much! :>>>>
"Jonas Klemming" <[email protected]> wrote in message
news:[email protected]..
Fixed it.
I had mapped .wlforward to iisforward.dll instead of iisproxy.dll
/Jonas
"Jonas Klemming" <[email protected]> wrote in message
news:[email protected]..
I get an the following error message "The specified procedure could not
be
found." in my browser when trying to use the IIS-proxy plugin on WLS 6.1sp2
Windows 2000
Has anyone else encountered this message? Any solutions?
Regards,
Jonas Klemming

WLS 6.1 SP2 and Apache 1.3.26 Windows NT/2000

Hi,
Is there an Apache plugin available for WLS 6.1 (SP2) and Apache 1.3.26 running
on Windows NT/2000?
thanks

I've solved my own problem. I learned that there was a sp4 (let alone a
sp3) for WLS. Installed that and the problem went away. Sorry for the
noise.
-Phil
Philip Bower <[email protected]> wrote in
news:[email protected]:
When I try to deploy the struts-example.war or if I add the struts.jar
to any other web app I've created, I get this error when I start WLS
and it tries to deploy that war.
java.lang.StringIndexOutOfBoundsException
at weblogic.servlet.internal.WebAppHelper.resolveManifestName
(WebAppHelper.java:469)
I'm using version 1.1b3 of struts. I'm having no problems with
version 1.0.2 of struts.
I'm guessing its complaining about the manifest file in struts.jar,
but I don't understand why.
Here's my version info and the stack trace (my web app is called
findme in this example). Thanks in advance.
-Phil
Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
#154529
<Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
application findme: Could not load findme>
<Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
starting Config caught throwable
java.lang.reflect.UndeclaredThrowableException:
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
at java.lang.String.substring(String.java:1525)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
.jav a:469)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
ava: 234)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
Serv letContext.java:3407)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
Cont ext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
t.ja va:862)

WLS 6.1 SP2 proxy server timeout

We are using WLS 6.1 SP2 server as a proxy server. When accessing a
page that has a long running process, the server times out in 5
minutes and throws an internal server error on the browser. Is there a
way to prevent this from happening or increase the timeout period?

We are using WLS 6.1 SP2 server as a proxy server. When accessing a
page that has a long running process, the server times out in 5
minutes and throws an internal server error on the browser. Is there a
way to prevent this from happening or increase the timeout period?

WLS 6.1 SP2 Cluster fails

          Hi All.
          we have migrated to WLS 6.1 SP2, now we have a serious problem with the cluster
          wihch die after several minutes. Our architecture is several front-ends servers
          (concretely servelts, without cluster) make request to back-end (starteles EJB,
          DB access). This back-end is compuond by four WLS instances running into 2 Sun
          Solaris Machines. The system reports the nexts messages in the weblogic.log.
          * backendPlatformA instance
          for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
          '#|platformA|129.1027407260379', bound: 'false', dead: 'false'" because
          of soft disconnect timeout.>
          ####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
          <platformA> <ExecuteThread: '117' for queue: 'default'> <system> <>
          <000000> <Tried to renew lease on lost reference: '257'>
          * backendPlatformB instance
          for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
          '#|platformB|118.1027407423933', bound: 'false', dead: 'false'" because
          of soft disconnect timeout.>
          ####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
          <platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
          <Removing "ClientContext - id: '#|platformB|119.1027407423933', bound:
          'false', dead: 'false'" because of soft disconnect timeout.>
          * ioboxPlatfromC instance
          for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
          '#|platformC|139.1027407286958', bound: 'false', dead: 'false'" because
          of soft disconnect timeout.>
          ####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
          <platformC> <ExecuteThread: '119' for queue: 'default'> <system> <>
          <000000> <Tried to renew lease on lost reference: '257'>
          * Instancia ioboxPlatfromD
          for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
          '#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
          of soft disconnect timeout.>
          ####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
          <platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
          <Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
          'false', dead: 'false'" because of soft disconnect timeout.>
          ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
          <ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
          platformA
          jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
          from cluster view due to PeerGone>
          ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
          <ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
          7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
          to the cluster>
          ####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
          <platformD> <ExecuteThread: '102' fo
          r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
          anaydidos>
          ####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
          <platformD> <ExecuteThread: '119' for queue: 'default'> <system> <>
          <000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because of:
          'Server received a message over an uninitialized connection: 'JVMMessage
          from: 'null' to:
          '1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
          cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
          flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
          Any idea?
          Thanks for all


          Hi,
          We are using Weblogic 6.1 SP2, NT 4.0 and java 1.3.1. We have also encountered
          the same error message. We have 1 admin and 2 managed servers. We have tried connecting
          in using weblogic.admin to check the idle thread and we are able to connect. However,
          when we connect from IIS to Weblogic, the application failed to response. We have
          tried connect direct to weblogic but it does not response as well. We have seen
          that the idle thread left has been reduced but there is no activites from the
          weblogic console. The thread is used but not releasing and the console is not
          moving. When we shutdown one of the managed server, the application is able to
          process as seen from the console.
          We have turned off native io and this behavior is not seen. When we turn on native
          io, it appear. So we can conclude that it is related to native io.
          Is there any solution or intermediate patch without upgrading to the later SP
          Thanks
          Rajesh Mirchandani <[email protected]> wrote:
          >We are shipping the Jdriver for oracle 816 with SP3. Use the driver
          >from .\bin\oci816_8
          >
          >Manuel wrote:
          >
          >> Thanks Rajesh,
          >>
          >> we have another problem since our database is Oracle 8.1.6 and SP3
          >jDriver doesn´t
          >> support this version.
          >>
          >> Best Regards
          >>
          >> Rajesh Mirchandani <[email protected]> wrote:
          >> >Upgrade to SP3, if possible.
          >> >
          >> >Manuel wrote:
          >> >
          >> >> Hi All.
          >> >>
          >> >> we have migrated to WLS 6.1 SP2, now we have a serious problem with
          >> >the cluster
          >> >> wihch die after several minutes. Our architecture is several front-ends
          >> >servers
          >> >> (concretely servelts, without cluster) make request to back-end
          >(starteles
          >> >EJB,
          >> >> DB access). This back-end is compuond by four WLS instances running
          >> >into 2 Sun
          >> >> Solaris Machines. The system reports the nexts messages in the weblogic.log.
          >> >>
          >> >> * backendPlatformA instance
          >> >>
          >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
          >id:
          >> >> '#|platformA|129.1027407260379', bound: 'false', dead: 'false'"
          >because
          >> >> of soft disconnect timeout.>
          >> >> ####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
          >> >> <platformA> <ExecuteThread: '117' for queue: 'default'> <system>
          ><>
          >> >> <000000> <Tried to renew lease on lost reference: '257'>
          >> >>
          >> >> * backendPlatformB instance
          >> >>
          >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
          >id:
          >> >> '#|platformB|118.1027407423933', bound: 'false', dead: 'false'"
          >because
          >> >> of soft disconnect timeout.>
          >> >> ####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
          >> >> <platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
          >> >> <Removing "ClientContext - id: '#|platformB|119.1027407423933',
          >bound:
          >> >> 'false', dead: 'false'" because of soft disconnect timeout.>
          >> >>
          >> >> * ioboxPlatfromC instance
          >> >>
          >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
          >id:
          >> >> '#|platformC|139.1027407286958', bound: 'false', dead: 'false'"
          >because
          >> >> of soft disconnect timeout.>
          >> >> ####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
          >> >> <platformC> <ExecuteThread: '119' for queue: 'default'> <system>
          ><>
          >> >> <000000> <Tried to renew lease on lost reference: '257'>
          >> >>
          >> >> * Instancia ioboxPlatfromD
          >> >>
          >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
          >id:
          >> >> '#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
          >> >> of soft disconnect timeout.>
          >> >> ####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
          >> >> <platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
          >> >> <Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
          >> >> 'false', dead: 'false'" because of soft disconnect timeout.>
          >> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
          >> >> <ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
          >> >> platformA
          >> >> jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
          >> >> from cluster view due to PeerGone>
          >> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
          >> >> <ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
          >> >> 7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
          >> >> to the cluster>
          >> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
          >> >> <platformD> <ExecuteThread: '102' fo
          >> >> r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
          >> >> anaydidos>
          >> >> ####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
          >> >> <platformD> <ExecuteThread: '119' for queue: 'default'> <system>
          ><>
          >> >> <000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because
          >> >of:
          >> >> 'Server received a message over an uninitialized connection: 'JVMMessage
          >> >> Wrom: HJEXXIMQZU
          >> >> '1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
          >> >> cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
          >> >> flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
          >> >>
          >> >> Any idea?
          >> >>
          >> >> Thanks for all
          >> >
          >> >--
          >> >Rajesh Mirchandani
          >> >Developer Relations Engineer
          >> >BEA Support
          >> >
          >> >
          >
          >--
          >Rajesh Mirchandani
          >Developer Relations Engineer
          >BEA Support
          >
          >

WLS 6.1 SP2 and JDK 1.4.0

In configuring our WLS 6.1 SP2 to run on the released JDK 1.4 and starting the
server, most things seemed to start fine except for our ObjectIDFactorySession
EJB. It cacked when it tried to create a bean in the free pool. Stack trace
below. I know this is not supported, but can anyone shed some light?
####<Feb 15, 2002 3:05:03 PM EST> <Warning> <EJB> <023app11> <port7011server>
<main> <system> <> <010063> <The EJB: ObjectIDFactorySession had an <initial-beans-in-free-pool>
setting in its weblogic-ejb-jar.xml. An error occurred while creating these initial
bean instances. The error was:
nulljava.lang.ExceptionInInitializerError
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:296)
     at java.lang.Class.newInstance(Class.java:249)
     at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:339)
     at javax.rmi.CORBA.Util.<clinit>(Util.java:51)
     at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:179)
     at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)
     at prototype.com.guardian.util.HomeFactory.createHome(HomeFactory.java:81)
     at prototype.com.guardian.util.HomeFactory.newHome(HomeFactory.java:49)
     at prototype.com.guardian.util.HomeFactory.newSession(HomeFactory.java:95)
     at prototype.com.guardian.fw.ObjectIDFactorySessionBean.ejbCreate(ObjectIDFactorySessionBean.java:31)
     at prototype.com.guardian.fw.ObjectIDFactorySessionBean_r4ogoq_Impl.ejbCreate(ObjectIDFactorySessionBean_r4ogoq_Impl.java:112)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:153)
     at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:198)
     at weblogic.ejb20.pool.Pool.onAfterDeploy(Pool.java:177)
     at weblogic.ejb20.deployer.Deployer.runAfterDeploymentListeners(Deployer.java:1325)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1013)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
     at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy65.addTarget(Unknown Source)
     at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
     at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
     at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:278)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy5.start(Unknown Source)
     at weblogic.management.Admin.startApplicationManager(Admin.java:1184)
     at weblogic.management.Admin.finish(Admin.java:590)
     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
     at weblogic.Server.main(Server.java:35)
Caused by: java.lang.RuntimeException: could not find or instantiate any UtilDelegate
class
     at weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:73)
     ... 77 more
>

I've solved my own problem. I learned that there was a sp4 (let alone a
sp3) for WLS. Installed that and the problem went away. Sorry for the
noise.
-Phil
Philip Bower <[email protected]> wrote in
news:[email protected]:
When I try to deploy the struts-example.war or if I add the struts.jar
to any other web app I've created, I get this error when I start WLS
and it tries to deploy that war.
java.lang.StringIndexOutOfBoundsException
at weblogic.servlet.internal.WebAppHelper.resolveManifestName
(WebAppHelper.java:469)
I'm using version 1.1b3 of struts. I'm having no problems with
version 1.0.2 of struts.
I'm guessing its complaining about the manifest file in struts.jar,
but I don't understand why.
Here's my version info and the stack trace (my web app is called
findme in this example). Thanks in advance.
-Phil
Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
#154529
<Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
application findme: Could not load findme>
<Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
starting Config caught throwable
java.lang.reflect.UndeclaredThrowableException:
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
at java.lang.String.substring(String.java:1525)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
.jav a:469)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
ava: 234)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
Serv letContext.java:3407)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
Cont ext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
t.ja va:862)

When will WLS 8.1 SP2 be GA ?

Similar Messages

Maybe you are looking for