WLS 7.0 SP2 Cluster deployment problems

I am having problems deploying our application to a weblogic cluster. Environment is
windows 2000/XP and weblogic 7.0 SP2.
Here's a simplified version of the cluster.
I have 2 managed servers that are part of the cluster.I have defined the managed server
configuration in the admin server's config.xml as below.
<Server Cluster="myCluster" ExpectedToRun="false" ListenPort="7771"
Machine="machine1" Name="Server1" ServerVersion="7.0.2.0"
WeblogicPluginEnabled="false" XMLEntityCache="XMLCacheMBean_Server1">
<COM Name="Server1"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="Server1"/>
<JTAMigratableTarget Cluster="myCluster" Name="Server1" UserPreferred
er="Server1"/>
<JTARecoveryService Name="Server1"/>
<KernelDebug Name="Server1"/>
<Log Name="Server1"/>
<SSL Enabled="false" ListenPort="7772" Name="Server1"/>
<ServerDebug Name="Server1"/>
<ServerStart Name="Server1"/>
<WebServer Name="Server1"/>
</Server>
<Server Cluster="myCluster" ExpectedToRun="false" ListenPort="7771"
Machine="machine2" Name="Server2" ServerVersion="7.0.2.0"
WeblogicPluginEnabled="false" XMLEntityCache="XMLCacheMBean_Server2">
<COM Name="Server2"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="Server2"/>
<JTAMigratableTarget Cluster="myCluster" Name="Server2" UserPreferred
er="Server2"/>
<JTARecoveryService Name="Server2"/>
<KernelDebug Name="Server2"/>
<Log Name="Server2"/>
<SSL Enabled="false" ListenPort="7772" Name="Server2"/>
<ServerDebug Name="Server2"/>
<ServerStart Name="Server2"/>
<WebServer Name="Server2"/>
</Server>
<Server AcceptBacklog="50" HelpPageURL="c:/public/as"
InstrumentStackTraceEnabled="true"
JDBCLogFileName="myserver\jdbc.log" JDBCLoggingEnabled="false"
ListenPort="7770" LogRemoteExceptionsEnabled="true"
LoginTimeout="1000" Machine="MyMachine" Name="myserver"
NativeIOEnabled="false" ReverseDNSAllowed="false"
ServerVersion="7.0.2.0" StdoutDebugEnabled="true"
StdoutEnabled="true" StdoutSeverityLevel="32"
SystemPassword="{3DES}2LwBLCayHcc="
ThreadPoolPercentSocketReaders="99" TunnelingClientPingSecs="45"
TunnelingClientTimeoutSecs="40" TunnelingEnabled="false"
WorkspaceShowUserKeysOnly="false"
XMLEntityCache="XMLCacheMBean_myserver" XMLRegistry="company XMLRegist
<COM Name="myserver"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="myserver"/>
<JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="
rver"/>
<JTARecoveryService Name="myserver"/>
<KernelDebug Name="myserver"/>
<Log FileMinSize="4096" FileName="myserver\company.log"
FileTimeSpan="24" Name="myserver"
NumberOfFilesLimited="true" RotationType="bySize"/>
<SSL ListenPort="7775" Name="myserver"/>
<ServerDebug Name="myserver"/>
<ServerStart Name="myserver"/>
<WebServer DefaultWebApp="go" LogFileName="myserver\access.log"
LoggingEnabled="true" Name="myserver" Targets="myserver"/>
</Server>
<ShutdownClass ClassName="company.appserver.weblogic.companyStartup"
DeploymentOrder="600" Name="companyShutdown2"
Targets="myCluster,Server1,Server2,myserver"/>
<ShutdownClass
ClassName="company.appserver.weblogic.WLTaskManagerInit"
DeploymentOrder="675" Name="TaskManagerShutdown" Targets="Server2"/>
<StartupClass ClassName="company.appserver.weblogic.ContextHandler"
DeploymentOrder="105" FailureIsFatal="true"
Name="ContextHandlerStartup1" Targets="myserver"/>
<XMLEntityCache Name="XMLCacheMBean"/>
<XMLEntityCache Name="XMLCacheMBean_Server1"/>
<XMLEntityCache Name="XMLCacheMBean_Server2"/>
<XMLEntityCache Name="XMLCacheMBean_myserver"/>
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactory
Name="company XMLRegistry"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl" Transf
rFactory="org.apache.xalan.processor.TransformerFactoryImpl"/>
/Domain>
The managed server config.xml looks like below.
$ cat config.xml
<?xml version="1.0" encoding="UTF-8"?>

<Domain ConfigurationVersion="7.0.2.0" Name="company">
<Application Deployed="true" Name="AGENTMANAGER"
Path=".\deployments\activity" TwoPhase="false">
<EJBComponent DeploymentOrder="20" Name="AGENTMANAGER"
Targets="Server2" URI="AGENTMANAGER.jar"/>
</Application>
<Application Deployed="true" Name="MDBERT1"
Path=".\deployments\service" TwoPhase="false">
<EJBComponent DeploymentOrder="46" Name="MDBERT1"
Targets="Server2" URI="MDBERT1.jar"/>
</Application>
<Application Deployed="true" Name="TM" Path=".\deployments\service" TwoPhase
="false">
<EJBComponent DeploymentOrder="15" Name="TM.jar"
Targets="Server2" URI="TM.jar"/>
</Application>
</Application>
<Application Deployed="true" Name="go" Path=".\applications"
StagedTargets="" TwoPhase="false">
<WebAppComponent Name="go" Targets="Server2" URI="go"/>
</Application>
<Application Deployed="true" Name="im" Path=".\applications"
StagedTargets="" TwoPhase="false">
<WebAppComponent Name="im" Targets="Server2" URI="im"/>
</Application>
<Application Deployed="true" Name="pmcl" Path=".\applications"
StagedTargets="" TwoPhase="false">
<WebAppComponent Name="pmcl" Targets="Server2" URI="pmcl"/>
</Application>
<ApplicationManager Name="company"/>
<CachingRealm ACLCacheEnable="true" ACLCacheSize="2000"
ACLCacheTTLNegative="60" ACLCacheTTLPositive="60"
AuthenticationCacheEnable="false" AuthenticationCacheSize="211"
AuthenticationCacheTTLNegative="10"
AuthenticationCacheTTLPositive="60" BasicRealm="companyRealm"
CacheCaseSensitive="true" GroupCacheEnable="true"
GroupCacheSize="100" GroupCacheTTLNegative="60"
GroupCacheTTLPositive="60" GroupMembershipCacheTTL="17700"
Name="companyCacheRealm" PermissionCacheEnable="true"
PermissionCacheSize="211" PermissionCacheTTLNegative="10"
PermissionCacheTTLPositive="60" UserCacheEnable="true"
UserCacheSize="2000" UserCacheTTLNegative="60" UserCacheTTLPositive="60"
/>
<CustomRealm Name="companyRealm" Password="{3DES}2LwBLCayHcc=" RealmClassName
="company.appserver.weblogic.WLRealmStub"/>
<EmbeddedLDAP
Credential="{3DES}VW4H4+7OUny8Er78dGhHbIqbB6w7l9btTnLbz4Cu1jE=" Name="Cy
gent"/>
<FileRealm Name="myFileRealm"/>
<JDBCConnectionPool CapacityIncrement="2"
DriverName="weblogic.jdbc.oci.Driver" InitialCapacity="5"
MaxCapacity="100" Name="Geneva0"
PreparedStatementCacheSize="100"
Properties="user=admin;password=;server=LSUP1"
Targets="Server2" URL="jdbc:weblogic:oracle"/>
<JDBCConnectionPool CapacityIncrement="2"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="5"
MaxCapacity="100" Name="JMSDBConnectionPool"
PreparedStatementCacheSize="100"
Properties="user=admin;password=gent;url=jdbc:oracle:thin:@x.x.x.179:1521:SUP1;dll=ocijdbc8;dataSourceName=ejbPool;protocol=thin"
Targets="Server2" URL="jdbc:oracle:thin:@x.x.x.x:1521:LSUP1"/>
<JDBCConnectionPool CapacityIncrement="2"
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="5" MaxCapacity="100" Name="ejbPool"
PreparedStatementCacheSize="100"
Properties="user=company_admin;url=jdbc:oracle:thin:@10.28.138.179:1521:P
MCLSUP1;password=company;dll=ocijdbc8;dataSourceName=ejbPool;protocol=thin"
SupportsLocalTransaction="true" Targets="Server2,Server2" URL="jdbc:orac
le:thin:@x.x.x.x:1521:LSUP1"/>
<JDBCDataSource JNDIName="geneva.jdbc.GenevaNonTrans0"
Name="GenevaNonTrans0" PoolName="Geneva0" Targets="Server2"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="geneva.jdbc.Geneva0" Name="Geneva0" PoolName="Geneva0" Targets
="Server2"/>
<JDBCTxDataSource EnableTwoPhaseCommit="false"
JNDIName="authJtsDataSource" Name="authJtsDataSource"
PoolName="ejbPool" Targets="Server2"/>
<JMSConnectionFactory DefaultRedeliveryDelay="5000"
DefaultTimeToDeliver="3000" JNDIName="company.ctm.QCFactory"
Name="CTMQCFactory" Targets="Server2"
UserTransactionsEnabled="true" XAConnectionFactoryEnabled="true"/>
<JMSConnectionFactory DefaultRedeliveryDelay="5000"
DefaultTimeToDeliver="3000" JNDIName="company.im.QCFactory"
Name="QCFactory" Targets="Server2"/>
<JMSConnectionFactory DefaultRedeliveryDelay="5000"
DefaultTimeToDeliver="3000" JNDIName="company.im.TCFactory"
Name="TCFactory" Targets="Server2"/>
<JMSJDBCStore ConnectionPool="JMSDBConnectionPool"
Name="companyCTMJDBCStore" PrefixName="CTM"/>
<JMSJDBCStore ConnectionPool="JMSDBConnectionPool"
Name="companyJMSJDBCStore" PrefixName="IM"/>
<JMSServer Name="CIM JMSServer-0" Store="companyJMSJDBCStore" Targets="Server
2">
<JMSQueue JNDIName="javax.jms.inRequestQueue" Name="inRequestQueue"/>
<JMSQueue JNDIName="javax.jms.inResponseQueue" Name="inResponseQueue"/>
<JMSQueue JNDIName="javax.jms.logQueue" Name="logQueue"/>
<JMSQueue JNDIName="javax.jms.outRequestQueue" Name="outRequestQueue"/>
<JMSQueue JNDIName="javax.jms.outResponseQueue" Name="outResponseQueue"/
>
<JMSSessionPool ConnectionFactory="company.im.QCFactory"
ListenerClass="company.service.mg.impl.InboundMsgListener"
Name="InboundRequestSessionPool" SessionsMaximum="5">
<JMSConnectionConsumer
Destination="javax.jms.inRequestQueue"
MessagesMaximum="10" Name="InboundRequestSessionPool" Selector="
TRUE"/>
</JMSSessionPool>
<JMSSessionPool ConnectionFactory="company.im.QCFactory"
ListenerClass="company.service.mg.impl.InboundMsgListener"
Name="InboundResponseSessionPool" SessionsMaximum="5">
<JMSConnectionConsumer
Destination="javax.jms.inResponseQueue"
MessagesMaximum="10"
Name="InboundResponseConnectionConsumer" Selector="TRUE"/>
</JMSSessionPool>
<JMSSessionPool ConnectionFactory="company.im.QCFactory"
ListenerClass="pmcl.company.service.mg.impl.PmclOutboundMsgListener"
Name="OutboundRequestSessionPool" SessionsMaximum="5">
<JMSConnectionConsumer
Destination="javax.jms.outRequestQueue"
MessagesMaximum="10"
Name="OutboundRequestConnectionPool" Selector="TRUE"/>
</JMSSessionPool>
<JMSSessionPool ConnectionFactory="company.im.QCFactory"
ListenerClass="pmcl.company.service.mg.impl.PmclOutboundMsgListener"
Name="OutboundResponseSessionPool" SessionsMaximum="5">
<JMSConnectionConsumer
Destination="javax.jms.outResponseQueue"
MessagesMaximum="10"
Name="OutboundResponseConnectionConsumer" Selector="TRUE"/>
</JMSSessionPool>
<JMSTopic JNDIName="javax.jms.CreateOfferTopic" Name="createOfferTopic"/
>
<JMSTopic JNDIName="javax.jms.CreateProductTopic" Name="createProductTop
ic"/>
</JMSServer>
<JMSServer Name="JMSServer-0">
<JMSQueue JNDIName="javax.jms.logQueue" Name="logQueue"/>
</JMSServer>
<JMSServer DeploymentOrder="1" Name="Task Manager Server-1"
Store="companyCTMJDBCStore" Targets="Server2">
<JMSQueue ErrorDestination="ERT1 Queue" JNDIName="activate_task"
Name="AT1 Queue" RedeliveryLimit="5"/>
<JMSQueue JNDIName="complete_process_flow" Name="CPF1 Queue" RedeliveryL
imit="5"/>
<JMSQueue ErrorDestination="ERT1 Queue" JNDIName="complete_task"
Name="CT1 Queue" RedeliveryLimit="5"/>
<JMSQueue JNDIName="error_task" Name="ERT1 Queue" RedeliveryLimit="1"/>
<JMSQueue ErrorDestination="ERT1 Queue" JNDIName="escalate_task"
Name="ET1 Queue" RedeliveryLimit="5"/>
<JMSQueue JNDIName="recover_process_flow" Name="RPF1 Queue" RedeliveryLi
mit="5"/>
<JMSQueue JNDIName="terminate_process_flow" Name="TPF1 Queue" Redelivery
Limit="5"/>
<JMSQueue ErrorDestination="ERT1 Queue"
JNDIName="terminate_task" Name="TT1 Queue" RedeliveryLimit="5"/>
</JMSServer>
<JTA Name="company" TimeoutSeconds="3600"/>
<Log FileName="./logs/company.log" Name="company"/>
<Machine Name="MyMachine">
<NodeManager Name="MyMachine"/>
</Machine>
<PasswordPolicy MinimumPasswordLength="8" Name="mypasswordpolicy"/>
<Realm CachingRealm="companyCacheRealm" FileRealm="myFileRealm" Name="myRealm
"/>
<SNMPAgent Name="company"/>
<Security CompatibilityMode="true" Name="company"
PasswordPolicy="mypasswordpolicy" Realm="myRealm" RealmSetup="true"/>
<SecurityConfiguration Credential="{3DES}Osb3tCLDbyc="
CredentialGenerated="false" Name="company"/>
<Server HelpPageURL="c:/public/as" InstrumentStackTraceEnabled="true"
JDBCLogFileName="Server2\jdbc.log" JDBCLoggingEnabled="false"
ListenPort="7771" LogRemoteExceptionsEnabled="true"
LoginTimeout="1000" Machine="MyMachine" Name="Server2"
NativeIOEnabled="true" ReverseDNSAllowed="false"
ServerVersion="7.0.2.0" StdoutDebugEnabled="true"
StdoutEnabled="true" StdoutSeverityLevel="32"
SystemPassword="{3DES}2LwBLCayHcc="
ThreadPoolPercentSocketReaders="99" TunnelingClientPingSecs="45"
TunnelingClientTimeoutSecs="40" TunnelingEnabled="false"
WorkspaceShowUserKeysOnly="false"
XMLEntityCache="XMLCacheMBean_Server2" XMLRegistry="company XMLRegistry">
<COM Name="Server2"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="Server2"/>
<JTAMigratableTarget Cluster="myCluster" Name="Server2" UserPreferredSer
ver="Server2"/>
<JTARecoveryService Name="Server2"/>
<KernelDebug Name="Server2"/>
<Log FileMinSize="4096" FileName="Server2\company.log"
FileTimeSpan="24" Name="Server2"
NumberOfFilesLimited="true" RotationType="bySize"/>
<SSL ListenPort="7772" Name="Server2"/>
<ServerDebug Name="Server2"/>
<ServerStart Name="Server2"/>
<WebServer DefaultWebApp="go" LogFileName="Server2\access.log"
LoggingEnabled="true" Name="Server2" Targets="Server2"/>
</Server>
<ShutdownClass ClassName="company.appserver.weblogic.companyStartup"
DeploymentOrder="200" Name="companyShutdown2" Targets="Server2"/>
<ShutdownClass
ClassName="company.appserver.weblogic.WLTaskManagerInit"
DeploymentOrder="175" Name="TaskManagerShutdown" Targets="Server2"/>
<StartupClass ClassName="company.appserver.weblogic.ContextHandler"
DeploymentOrder="105" FailureIsFatal="true"
Name="ContextHandlerStartup1" Targets="Server2"/>
<StartupClass ClassName="company.appserver.weblogic.companyStartup"
DeploymentOrder="100" FailureIsFatal="true"
Name="companyStartup1" Targets="Server2,Server2"/>
<StartupClass
ClassName="company.appserver.weblogic.WLTaskManagerInit"
DeploymentOrder="125" FailureIsFatal="true"
Name="TaskManagerStartup" Targets="Server2"/>
<XMLEntityCache Name="XMLCacheMBean"/>
<XMLEntityCache Name="XMLCacheMBean_Server2"/>
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImp
l"
Name="company XMLRegistry"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl" Transform
erFactory="org.apache.xalan.processor.TransformerFactoryImpl"/>
</Domain>
I start the admin server first followed by one of the managed servers. The admin server
starts fine. When I start the managed server 1, it is not deploying the application on the
managed server and I am getting the following exception on the managed server.
Setting custom initial context factory<Nov 25, 2004 11:54:44 PM CET> <Notice> <Management> <141053> <Application Polle
r not started for production server.>
<Nov 25, 2004 11:54:45 PM CET> <Notice> <Management> <141030> <Starting discover
y of Managed Server... This feature is on by default, you may turn this off by p
assing -Dweblogic.management.discover=false>
<Nov 25, 2004 11:54:45 PM CET> <Notice> <WebLogicServer> <000354> <Thread "Liste
nThread.Default" listening on port 7770>
<Nov 25, 2004 11:55:06 PM CET> <Warning> <RJVM> <000519> <Unable to connect to a
remote server on address x.x.x.x and port 7771 with protocol t3. The Exce
ption is java.net.ConnectException: Connection refused: connect>
<Nov 25, 2004 11:55:06 PM CET> <Warning> <Management> <141028> <Unable to locate
Managed server Server2 on listen address x.x.x.223 listen port 7771. Ignore
this message if the Managed server was shutdown intentionally. The Managed serv
er will connect to the Admin server when it is re-started.>
<Nov 25, 2004 11:55:08 PM CET> <Warning> <RJVM> <000519> <Unable to connect to a
remote server on address x.x.x.222 and port 7771 with protocol t3. The Exce
ption is java.net.ConnectException: Connection refused: connect>
<Nov 25, 2004 11:55:08 PM CET> <Warning> <Management> <141028> <Unable to locate
Managed server Server1 on listen address x.x.x.222 listen port 7771. Ignore
this message if the Managed server was shutdown intentionally. The Managed serv
er will connect to the Admin server when it is re-started.>
<Nov 25, 2004 11:55:08 PM CET> <Notice> <WebLogicServer> <000329> <Started WebLo
gic Admin Server "myserver" for domain "company" running in Production Mode>
<Nov 25, 2004 11:55:09 PM CET> <Notice> <WebLogicServer> <000365> <Server state
changed to RUNNING>
<Nov 25, 2004 11:55:09 PM CET> <Notice> <WebLogicServer> <000360> <Server starte
d in RUNNING mode>
<Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
ing;Ljava.lang.String;)
javax.management.InstanceNotFoundException: company:Name=Server1,Type=Migratable
Target
javax.management.InstanceNotFoundException: company:Name=Server1,Type=MigratableT
arget
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
a:144)
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
a:268)
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
meImpl.java:288)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:821)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:308)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
<Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
ing;Ljava.lang.String;)
javax.management.InstanceNotFoundException: company:Name=Server2,Type=Migratable
Target
javax.management.InstanceNotFoundException: company:Name=Server2,Type=MigratableT
arget
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
a:144)
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
a:268)
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
meImpl.java:288)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:821)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:308)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
<Nov 25, 2004 11:56:57 PM CET> <Warning> <rmi> <080005> <Exception thrown by rmi
server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljava.lang.Str
ing;Ljava.lang.String;)
javax.management.InstanceNotFoundException: company:Name=Server2,Type=Migratable
Target
javax.management.InstanceNotFoundException: company:Name=Server2,Type=MigratableT
arget
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
a:144)
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.jav
a:268)
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHo
meImpl.java:288)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:821)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:308)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
Can somebody help me find out why this problem is occuring..?

Similar Messages

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, Error Deploying WAR, Manifest file problem

Hi,
When I moved to SP2 on 6.1, I am getting a new error while deploying a war file.
It looks from the stack trace that there is a problem with my manifest file, but
I am just taking the manifest file created by jdk1.3 jar utility - My META-INF
dir is empty before jarring. When opened in notepad, the cursor can go to the
start of the line below the blank line. I mention this in case that is the EOF,
and relevant to the problem. Any help is much appreciated.
Mike
Manifest File:
Manifest-Version: 1.0
Created-By: 1.3.1 (Sun Microsystems Inc.)
Stack Trace:
####<Feb 22, 2002 10:32:36 AM EST> <Info> <HTTP> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101031> <[WebAppServletContext(1118014,ipp,/ipp)]
extracting classfiles to C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_myserver_myserver_ipp:>
####<Feb 22, 2002 10:32:36 AM EST> <Debug> <HTTP> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101158> <Exception
thrown while loading ipp: java.lang.StringIndexOutOfBoundsException: String index
out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
 at java.lang.String.substring(String.java:1525)
 at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
 at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
 at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
 at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
 at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
 at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
 at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
 at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
 at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
 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 weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
 at java.lang.reflect.Method.invoke(Native Method)
 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 $Proxy32.addWebDeployment(Unknown Source)
 at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
 at java.lang.reflect.Method.invoke(Native Method)
 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 $Proxy98.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 java.lang.reflect.Method.invoke(Native Method)
 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.update(Unknown Source)
 at weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
 at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
 at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
 at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
 at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
 at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 22, 2002 10:32:36 AM EST> <Error> <J2EE> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <160001> <Error deploying
application ipp: Could not load ipp>
####<Feb 22, 2002 10:32:36 AM EST> <Error> <Management> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <141042> <Error deploying
application .\config\mydomain\applications\ipp.war: java.lang.reflect.UndeclaredThrowableException>

I figured out what was causing this for me. Apparently, the new Manifest reader
classes in WLS SP2 are a lot pickier ( polite way of saying they dont handle exception
cases very well ;-) ). I had 2 third-party jar files in my WEB-INF/lib directory
whose manifests had issues that the Manifest reader could not handle. One of
them was a header line that wrapped and the other had extra lines at the end of
the file. I had to unjar them, fix the manifests, and re-jar them. the server
started up fine after that.
It might be nice if they provided a better error message than "String Index Out
Of Bounds: -1" for this problem, but hey, you can't have everything because where
would you put it :)
"Mike Dunbar" <[email protected]> wrote:
>
Hi,
When I moved to SP2 on 6.1, I am getting a new error while deploying
a war file.
It looks from the stack trace that there is a problem with my manifest
file, but
I am just taking the manifest file created by jdk1.3 jar utility - My
META-INF
dir is empty before jarring. When opened in notepad, the cursor can go
to the
start of the line below the blank line. I mention this in case that is
the EOF,
and relevant to the problem. Any help is much appreciated.
Mike
Manifest File:
Manifest-Version: 1.0
Created-By: 1.3.1 (Sun Microsystems Inc.)
Stack Trace:
####<Feb 22, 2002 10:32:36 AM EST> <Info> <HTTP> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101031> <[WebAppServletContext(1118014,ipp,/ipp)]
extracting classfiles to C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_myserver_myserver_ipp:>
####<Feb 22, 2002 10:32:36 AM EST> <Debug> <HTTP> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101158> <Exception
thrown while loading ipp: java.lang.StringIndexOutOfBoundsException:
String index
out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
 at java.lang.String.substring(String.java:1525)
 at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
 at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
 at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
 at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
 at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
 at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
 at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
 at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
 at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
 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 weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
 at java.lang.reflect.Method.invoke(Native Method)
 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 $Proxy32.addWebDeployment(Unknown Source)
 at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
 at java.lang.reflect.Method.invoke(Native Method)
 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 $Proxy98.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 java.lang.reflect.Method.invoke(Native Method)
 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.update(Unknown Source)
 at weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
 at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
 at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
 at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
 at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
 at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 22, 2002 10:32:36 AM EST> <Error> <J2EE> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <160001> <Error
deploying
application ipp: Could not load ipp>
####<Feb 22, 2002 10:32:36 AM EST> <Error> <Management> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <141042> <Error
deploying
application .\config\mydomain\applications\ipp.war: java.lang.reflect.UndeclaredThrowableException>

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.

BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

Hello anybody,
learnt XA being necessary if more than one sql command in transaction, so I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now I receive the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
start() failed on resource 'OracleDB' Unexpected error during start for XAResource
'OracleDB': null
 at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
 at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
 at weblogic.j2ee.Application.deploy(Application.java:247)
 at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
 at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
 at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
 at java.lang.reflect.Method.invoke(Native Method)
 at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
 at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
 at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Hi Klaus,
if you want to implement a global transaction over two different JDBC Resource Managers
(update on both + 2PC) they have to be both XA compliant.
Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
and configuring a TXDataSource with "enable two-phase commit" = true (but only one
non-XA JDBC driver at a time can participate in a distributed transaction).
Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
transactions or distributed transactions without XA drivers as well (using a single
resource manager).
But if you want to update multiple resource managers in the same transaction using
EJBs, this is a "global" transaction, and WL server fully supports it.
But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
Sergi
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
>
Hi Sergi, hello world,
thanks a lot for this message. So the conclusion is that I hava no chance
at all
to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
a prerequisite
for EJB are XA-transactions.
Is this conclusion correct.
Many thanks again
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
distributed transaction (XA) features require version
Oracle8i release 8.1.6 or later of the Oracle server.
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hi Sergi,
1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
2.) I didn´t use a special driver but that that was delivered with thewls
server
in the package "weblogic.jar".
Could I enable you helping me with this information?
Best wishes
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
which
1) Oracle server version (I don't think it's a 8.3.2.)
2) Oracle JDBC driver version
are you you using ?
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hello anybody,
learnt XA being necessary if more than one sql command in transaction,so
I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now
I
receive
the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating itsSQL
Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction
branch
start() failed on resource 'OracleDB' Unexpected error during start
for
XAResource
'OracleDB': null
 at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
 at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
 at weblogic.j2ee.Application.deploy(Application.java:247)
 at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
 at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
 at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
 at java.lang.reflect.Method.invoke(Native Method)
 at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
 at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
 at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

WLS 6.1 SP2 and Struts 1.1b3 Manifest Problem

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.java:
234)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServ
letContext.java:3407)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletCont
ext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.ja
va:862)
at
weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.
java:815)
at
weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
Target.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
Target.java:144)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java
:76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
l.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
anImpl.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 $Proxy29.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployme
nt(WebServerMBean_CachingStub.java:1121)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
Target.java:315)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen
tTarget.java:279)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(
DeploymentTarget.java:233)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy
mentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
l.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
anImpl.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 $Proxy28.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments
(ServerMBean_CachingStub.java:2761)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(App
licationManager.java:370)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManag
er.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
l.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
anImpl.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 $Proxy36.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start
(ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1180)
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)
--------------- nested within: ------------------
weblogic.j2ee.DeploymentException: Could not load findme - with nested
exception:
[java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
at
weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
Target.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
Target.java:144)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java
:76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
l.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
anImpl.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 $Proxy29.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployme
nt(WebServerMBean_CachingStub.java:1121)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
Target.java:315)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen
tTarget.java:279)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(
DeploymentTarget.java:233)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy
mentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
l.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
anImpl.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 $Proxy28.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments
(ServerMBean_CachingStub.java:2761)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(App
licationManager.java:370)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManag
er.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
l.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
anImpl.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 $Proxy36.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start
(ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1180)
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)
>
<Feb 11, 2003 7:45:32 AM EST> <Error> <J2EE> <Error deploying application
struts-example: Could notload struts-example>
<Feb 11, 2003 7:45:32 AM EST> <Error> <Management> <Error deploying
application .\config\mydomain\applications\struts-example.war:
java.lang.reflect.UndeclaredThrowableException>

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)

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

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

WLS 6.1 SP2, iPlanet 6 & NSAPI problems

Does anybody know of a good reference document on how to properly install the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references that
I have been finding are either incomplete, have typo's and are mostly Windows oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies, etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other, etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x then many
of the docs out there are inaccurate. Does anyone know if there is a newer version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix (Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas? Thanks!
-Doug

Hi Doug
U have to put the following section
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="./libproxy.so"
Init fn="wl_init"
into magus.conf
and put the rest into obj.conf
Best Regards
Alex
"Doug E" <[email protected]> wrote:
>
Does anybody know of a good reference document on how to properly install
the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references
that
I have been finding are either incomplete, have typo's and are mostly Windows
oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies,
etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many
of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other,
etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x
then many
of the docs out there are inaccurate. Does anyone know if there is a newer
version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc
from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix
(Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas?
Thanks!
-Doug

WLS 8.1 SP2 : node-to-node request routing in cluster???

Hello everybody;
 a bit confused about request management in WLS clusters,
 hope you can help clarify, please.
 Do WLS 8.1 SP2 clusters use node-to-node request
 routing "behind the scenes"?
 If so, can this feature be explicitly configured/controlled?
 TIA
 Paola R.

Paola R. <[email protected]> writes:
 > Hello everybody;
 >
 >
 > a bit confused about request management in WLS clusters,
 > hope you can help clarify, please.
 >
 >
 > Do WLS 8.1 SP2 clusters use node-to-node request
 > routing "behind the scenes"?
 Only in certain circumstances (usually becuase you are using an applet
 or the servers are behind a firewall). Usually routing is client
 driven.
 >
 >
 > If so, can this feature be explicitly configured/controlled?
 No
 andy
 >
 >
 > TIA
 >
 >
 > --
 > Paola R.

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 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)

Re: WLS 6.0 SP2 hangs due to many sockets in CLOSE_WAIT state

We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000 platform.
Currently we are using running some stablity tests and noticing that there are
lot of sockets in close_wait state and handle count keeps going up and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay as suggested
in this newsgroup, and we are still noticing this problem. Does any body have
the same issue?. is this a know problem with weblogic http server?. and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N

BEA acknowledges this problem in 6.0 SP2 with iPlanet plug-in.
Solution that they recommend is to use 6.1 SP2 plug-in (they claim
full compatibility). Also, you may have to set KeepAliveEnabled to
false in obj.conf (the problem is in wrong pooling).
Hope it helps,
Bala
Robert Patrick <[email protected]> wrote in message news:<[email protected]>...
There are a couple of issues.
1.) You need to tune the machine running the web server and the machine
running WebLogic to make sure that it is configured appropriately for a
high-volume HTTP server. See
http://e-docs.bea.com/wls/platforms/sun/index.html for details on tuning
Solaris.
2.) I believe that there is a bug in the plugins in 6.0 where it is not
properly closing sockets. Try using the plugin from WLS 6.1 SP2...
Hope this helps,
Robert
Kevin Phillips wrote:
Tim Funk <[email protected]> wrote:
I am experiencing similar problems with WL 6.0 SP2 on Solaris 2.6.
We are already proxying all HTTP traffic through a
cluster of apache servers. Unfortuantely, the apache-WL
bridge seems to work so efficiently that our servers are
still flooded with open sockets in the TCP_CLOSE_WAIT state.
It seems to be bound by WebLogic's capacity to respond to
the requests in a speedy enough fashion.
Anybody have any suggestions?
Kevin
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because
it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000
platform.
Currently we are using running some stablity tests and noticing that
there are
lot of sockets in close_wait state and handle count keeps going up
and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay
as suggested
in this newsgroup, and we are still noticing this problem. Does any
body have
the same issue?. is this a know problem with weblogic http server?.
and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N

WLS 7.0 SP2 stop response

The size of the ear is 43MB. It is deployed to WLS 70Sp2 successfully.
But after using the app for a few minutes (access the pages by IE 6.0), WLS stop
response: a white page is displayed(no text, no image, nothing displayed).
I want to see what hapened by type http://localhost:7001/console, the browser
also displayed a white page.(no login)
At the same time, I notice that the DOS console didnot display INFO log message
any more.
The app works fine on WLS 8.1.
I want to know it is caused by the bugs in my app or it is an issue of the configuration
of WLS.

There could be dozens of reasons for this; impossible to diagnose with so few details.
If you want to rule out known problems in WLS 7.0 SP2, then install SP3 and try again.
Wayne Scott
Guofeng Zhang wrote:
The size of the ear is 43MB. It is deployed to WLS 70Sp2 successfully.
But after using the app for a few minutes (access the pages by IE 6.0), WLS stop
response: a white page is displayed(no text, no image, nothing displayed).
I want to see what hapened by type http://localhost:7001/console, the browser
also displayed a white page.(no login)
At the same time, I notice that the DOS console didnot display INFO log message
any more.
The app works fine on WLS 8.1.
I want to know it is caused by the bugs in my app or it is an issue of the configuration
of WLS.

Deployment Problems of Enterprise Application in NWDS 7.1

Hello Everyone, 
 
I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer. SUMMARY 
~~~~~~~~~~~~~~~~~~~ 
Successfully deployed: 0 
Deployed with warnings: 0 
Failed deployments: 1 
~~~~~~~~~~~~~~~~~~~ 
ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it. 
 
1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear 
 Name:test~sgj_ent_app_test_three 
 Vendor:sap.com 
 Location:PDI_J2EETST1_D 
 Version:20100716152020 
 Deploy status:Aborted 
 Version:HIGHER 
 
 Description: 
 1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container. 
 
Exception: 
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
 at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
 at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 ... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 ... 12 more
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
 at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
 at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
 at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Edited by: Savin on Aug 5, 2010 10:25 PM
Edited by: Savin on Aug 5, 2010 10:26 PM
Edited by: Savin on Aug 5, 2010 10:31 PM
Edited by: Savin on Aug 5, 2010 5:27 PM
Edited by: Savin on Aug 5, 2010 5:38 PM
Edited by: Savin on Aug 5, 2010 5:44 PM

Hi Veera/Abhi
I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
On my NWDS PDA Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
2009-02-11 13:02:40 ... (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
Madhu--
Please find my ans to the following points mentioned by you
1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
It is assigned
2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
Rule is activated
3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
Rule is activated
4) Make sure that you have installed the following components in the following sequence in the PDA
- Creme
- MinDB/DB2e
- PDA_eswt_container
- PDA Runtime.
Client is installed in this sequence only. I referrred to help.sap.com while installing
the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking up the data. giving the above mentioned error.
Regards
Priya

WLS 7.0 SP2 Cluster deployment problems

Similar Messages

Maybe you are looking for