Weblogic Server 6.1 as an NT service - (post-install)

I've already installed Weblogic Server 6.1 not as an NT service.
For a new project I find I need it as an NT service. How can I register it as
an NT service without having to re-install (and lose my existing effort)?
J
Edited by LWCarl at 06/11/2008 8:53 AM

This link is better....
http://e-docs.bea.com/wls/docs61///adminguide/startstop.html#1026476
"J" wrote in message
news:3c437b4f$[email protected]..
>
I've already installed Weblogic Server 6.1 not as an NT service.
For a new project I find I need it as an NT service. How can I register itas
an NT service without having to re-install (and lose my existing effort)?
J--
Edited by jonmountjoy at 03/05/2008 5:42 AM
Edited by LWCarl at 06/11/2008 8:51 AM

Similar Messages

Weblogic Server 6.1 as Windows NT Service

Hi All,
I am running Weblogic Server 6.1 as Windows NT Service with one WAR
Application Deployed in Production Mode.
My machine is on Windows 2000 Application Server. I am facing a very strange
problem with the setup.
Prob 1 :
Sometimes the service unexpactedly terminates ( I ve got the log in
Event Viewer of Win2K saying that myserver service has been terminated 2
times....) !! Can anyone explain why it is terminating like these ? what
could be the possible reasons ?
Prob 2 :
When i see the logs that are generated i found that the WAR Application
is continuously getting re-deployed and I am getting Deployment Exceptions
for the same WAR files that i couldnt be deployed. This is happening
automatically , I am not re-deploying the app.
What could be the possible reasons ? Can anyone explain this behaviour ?
Thanks in Advance.
Bhavin Raichura

Hello Bhavin,
Are you sure you are running in production mode? Because production vs
development mode is controlled by a parameter in startWebLogic. However,
startWebLogic doesn't matter when you run it as a service. The startup
parameters are set in installNTService, from where they go directly in the
Windows registry.
We found out that it matters what the timestamp of the packaged file is,
compared to the time WebLogic started. For us, when the timestamp of our
.ear file is earlier than the time WebLogic started, it does not want to
redeploy. Maybe your timestamp is in the future or something??
There are two reasons why you will see "service terminated unexpectedly".
(a) If you stop the server yourself from the admin console or through the
command line, the beasvc process exits, but Windows doesn't expect that, so
it complains. Windows will not complain if you stop the service through "net
stop <service>".
However, there is reason (b), when the beasvc.exe process crashes by itself.
We occasionally experience that (WebLogic 6.1 sp1) and we don't know why
either. The only clue is in the weblogic.log file, where the last entry was
something like: NT Performance Pack, I/O error, FD 3456.
If you solve your #1, I would love to hear about it.
Christo
"bhavin raichura" <[email protected]> wrote in message
news:[email protected]...
Hi Kumar,
Thanks for the reply.
Well, the size of WAR is not very big, but that needs many other jars inthe
classpath to get executed.
I suppose the prob # 2 can be solved by Disabling Auto Deployment of
Applications from Console > Mydomain > Application and uncheck thecheckbox
but I am not sure.
But what is wrong exactly with the setup ? This works perfactly alrightwhen
Weblogic is not running as Windows Service.
can web.xml and weblogic.xml or config.xml be helpful to you in
understanding the problem ?
Thanks in advance.
Bhavin Raichura
"Kumar Allamraju" <[email protected]> wrote in message
news:[email protected]...
I can help with #2.
If your war file is not that big, can you send it to me? I will take alook at
it.
bhavin raichura wrote:
Hi All,
I am running Weblogic Server 6.1 as Windows NT Service with one WAR
Application Deployed in Production Mode.
My machine is on Windows 2000 Application Server. I am facing a very
strange
problem with the setup.
Prob 1 :
Sometimes the service unexpactedly terminates ( I ve got the log
in
Event Viewer of Win2K saying that myserver service has been terminated2
times....) !! Can anyone explain why it is terminating like these ?what
could be the possible reasons ?
Prob 2 :
When i see the logs that are generated i found that the WARApplication
is continuously getting re-deployed and I am getting DeploymentExceptions
for the same WAR files that i couldnt be deployed. This is happening
automatically , I am not re-deploying the app.
What could be the possible reasons ? Can anyone explain this behaviour
>>>
Thanks in Advance.
Bhavin Raichura

Problem running a jspx page on 11.1.2.4.0 on the integrated weblogic server with 11.1.1.6.0 already installed

hi friends,
i have installed a different version of JDev 11.1.2.4.0 as per my new job requirements and i am unable to run my .jspx page ... i already have 11.1.1.6.0 installed and running ... the following is the error that i am getting... can anyone help me with this....
"The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully".

I hope you did not install the 11.1.2.4.0 into the same middleware_home as you isstalled the 11.1.1.6.0. In this case you need to install both again.
If you installed the 11.1.2.4.0 into a different (empty) middleware home you should check the log file, which exact error occurred during the install. The location of the log can be found in the log window.
Anyway you should remove the system11.1.2.x.x.x/DefaultDomain before trying again.
Timo

Can't start weblogic server using Ant

Hello,
I can't start the WL Portal after installation.
On a Windows 2000 Server SP2 : - I installed WebLogic Server 6.1 SP2 with the examples
- I installed WebLogic Portal 4.0 SP2 (giving the same password as during the WL
Server installation) -I installed EBCC 4.0 SP2 .
I updated the license with UpdateLicense.cmd
Now If I run - run the default WL server, both from the menu and as a service -
enter the WL server console (on port 7001) - run the EBCC .
When I try to start the WL Portal, from the program menu I am able to start the
WP server properly , But I I try to start it from an ant wlrun then I get the error
an IllegalAccessError (with the same password I gave during installation and I use
to enter the server console): The WebLogic Server did not start up properly. Exception
raised: java.lang.IllegalAccessError: try to access method weblogic/management/internal/Helper.preloadMBeanInfos()V
from class weblogic/management/Admin at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35) Reason: Fatal initialization exception
Any idea ?

Hi VG,
thank u a lot for ur answer. But there are no files at the Admin Server boot.properties path.
and at the BI Server boot.properties path there is no security folder. Do u have any idea why i cant found anything at this directions ? Also I tried again the command "./startWeblogic.sh " and get a new error message which I post below. I am rlly worry about this. Is there maybe a way to reset the OBIEE and undo all changes ?
<Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Oct 30, 2013 10:00:48 AM CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
^C<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Oct 30, 2013 10:39:50 AM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Deploying the UPK recorded content in Peoplesoft Weblogic server.

Hi,
I have Peoplesoft UPK recoded content with me and also have document for configuring help menu with the UPK content.
It's appreciated If some one can help me in knowing steps (or) any documents for deploying the UPK recorded content in Peoplesoft Weblogic server.
Also I don't want to install PeopleBook in the weblogic server.
Thanks
Soundappan

There are two out of the box ways to enable UPK with PeopleSoft.
PeopleBooks > PeopleTools 8.52: PeopleTools Portal Technologies > Configuring UPK Topics as Related Content Services
PeopleBooks > PeopleTools 8.52: PeopleSoft Application Designer Developer's Guide > Configuring Embedded Help to Display UPK Content
Hope this helps.
Regards,
Hakan

How to run Weblogic Server 8.1 in Win 98/Red Hat Linux

I've receieved the Weblogic Server 8.1 Evaluation version. I've installed it successfully. But while I try to start the Weblogic Server the progress bar shows the completion of the server start but the indicator does not turn green. What might be the reason.Same is the problem with Red hat Linux 8.0 ? Please send in the solution

Joydeep,
WebLogic Platform 8.1 is not supported on Win 98 and Red Hat 8.0. Please
refer to the following url for more information.
http://e-docs.bea.com/platform/docs81/support/supp_plat.html#1048419
Regards,
Raj Alagumalai
WebLogic Workshop Support
"Joydeep Paul" <[email protected]> wrote in message
news:3f4e9723$[email protected]..
I've receieved the Weblogic Server 8.1 Evaluation version. I've installedit successfully. But while I try to start the Weblogic Server the progress
bar shows the completion of the server start but the indicator does not turn
green. What might be the reason.Same is the problem with Red hat Linux 8.0 ?
Please send in the solution

I can't install weblogic server 10.3 found error

I have install to 65% and found error.
i want to know why i can't install weblogic server 10.3 (may be error was create by jdk or anything else Please tell me! )
and how many problem that can happen when install weblogic server 10.3
ps. - OS that i install is windowsXP sp2

Without giving us any details about what error you got, or any circumstances of your environment (just the OS isn't enough), there is no way anyone could give you any help.

WebLogic server home location

I was trying to install WebLogic server 10 g.There I got page where they were asking to enter WebLogic server home location.
Which ever location i am giving , it is showing not a server home location.
Can you plz help me out?
What does WebLogic server home location exactly mean?
How to install WebLogic server 10 g?

Hi,
The WebLogic home is the root directory in which Oracle WebLogic Server is installed. A WebLogic Server home contains installed files necessary to host a WebLogic Server. The WebLogic Server home directory is a peer of Oracle home directories and resides within the directory structure of the Middleware home.
The WebLogic home directory contains only product binary files that are mostly read only until the files are either patched or upgraded.
mark if this helps you.
Regards,
Kishore

Problem in deploying Web Service Application on Weblogic Server

Hi,
I am trying to develop a web service application with eclipse, all things goes correct and wsdl also gets formed but the problem occurs when the EAR is deployed. It gives error in publishing the EAR file.
Here is the error i am getting:
Module named 'ftooldev1EAR' failed to deploy. See Error Log view for more detail.
*weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ftooldev1EAR:/ftooldev1)] Error parsing descriptor in Web appplication "D:\eclipse_wspace1\ftooldev1\build\jws\weboutput"*
*com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
*     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)*
*     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)*
*     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)*
*     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)*
*     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)*
*     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)*
*     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)*
*     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)*
*     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)*
*     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)*
*     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)*
*     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)*
*     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)*
*     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)*
*     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)*
*     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)*
*     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)*
*     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)*
*     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)*
*     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)*
*     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)*
*     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)*
*     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)*
*     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)*
*     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)*
*     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)*
*     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)*
*     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)*
*     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)*
*     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)*
*     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)*
*     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)*
*     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)*
*     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)*
*     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)*
*     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)*
*     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)*
*     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)*
*     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)*
*     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)*
*     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)*
*     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
*invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1075)
at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:132)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
*Caused by: weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ftooldev1EAR:/ftooldev1)] Error parsing descriptor in Web appplication "D:\eclipse_wspace1\ftooldev1\build\jws\weboutput"*
*com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
*invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.servlet.internal.WebAppModule.createModuleException(WebAppModule.java:1511)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1247)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
*Caused by: com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
Here is the web.xml of my application:
*<?xml version="1.0" encoding="UTF-8"?>*
*<web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"*
xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
*<servlet>*
*<servlet-name>action</servlet-name>*
*<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>*
*<init-param/>*
*</servlet>*
*<servlet>*
*<javaee:display-name>Apache-Axis Servlet</javaee:display-name>*
*<servlet-name>AxisServlet</servlet-name>*
*<servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class>*
*</servlet>*
*<servlet-mapping>*
*<servlet-name>AxisServlet</servlet-name>*
*<url-pattern>/servlet/AxisServlet</url-pattern>*
*</servlet-mapping>*
*<servlet-mapping>*
*<servlet-name>AxisServlet</servlet-name>*
*<url-pattern>*.jws</url-pattern>*
*</servlet-mapping>*
*<servlet-mapping>*
*<servlet-name>AxisServlet</servlet-name>*
*<url-pattern>/services/*</url-pattern>*
*</servlet-mapping>*
*<servlet>*
*<javaee:display-name>Axis Admin Servlet</javaee:display-name>*
*<servlet-name>AdminServlet</servlet-name>*
*<servlet-class>org.apache.axis.transport.http.AdminServlet</servlet-class>*
*<load-on-startup>100</load-on-startup>*
*</servlet>*
*<servlet-mapping>*
*<servlet-name>AdminServlet</servlet-name>*
*<url-pattern>/servlet/AdminServlet</url-pattern>*
*</servlet-mapping>*
*</web-app>*
Edited by: 925692 on Apr 5, 2012 1:38 AM
Edited by: 925692 on Apr 5, 2012 1:40 AM
Edited by: 925692 on Apr 5, 2012 1:40 AM

This behavior might be attributed to Axis inclusion.
Web service actions and wizards supported by Weblogic can be found at:
File->New->Other->Oracle->WebLogic->Web Services
Can you provide more detail about your starting point wsdl? or JWS? and information around what generation actions you used?
Thanks

PL/SQL Web Service fails when deployed to WebLogic server

I have a web service generated via JDeveloper from a PL/SQL package. It runs fine both when tested in JDeveloper and when the WAR file is manually deployed to the Integrated WebLogic Server. However, when the WAR file is deployed to our actual WebLogic server, it fails. Other existing web services that were not generated with the JDeveloper wizard work correctly. I am having trouble finding any references to this type of issue to solve it. Are there any ideas what might be causing the WSDL to fail?
References:
* JDeveloper 11.1.1.6.
* No proxies are involved.
* The PLSQL package is a basic function that returns varchar2 input fed in by one parameter:
create or replace package body pkg_ws_test as
function test_me (p_anything_in varchar2)
return varchar2 is
begin
return p_anything_in;
end test_me;
end pkg_ws_test;
* Top of error stack is as follows:
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
...

Hi,
The below error trace you've provided doesn't confirm that Weblogic server has thrown the error.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
Please paste complete stacktrace of the error to check and also include the caused by section in the error.
Thanks,
Vijaya

How to update Data Services (ALDSP 2.5) from WebLogic Server 9.2 correctly?

Hi,
I need to update some physical data service in ALDSP 2.5 on WLS 8.1 SP6 (8.1.6) via Static Mediator API from WebLogic Server 9.2 MP2 (9.2.2) application. I have reviewed the article about interoperability of ALDSP 2.5 and WLS 9 here:
http://edocs.bea.com/aldsp/docs25/appdev/ejbclt.html#wp1090900
Firstly, I had a problems with the interconnection between 9.2 client and ALDSP 2.5 due to some missed methods/classes. Finally, I've added the following libs to my WLS 9.2.2 pre-classpath in such an order:
MyDSPProject-ld-client.jar (built with Ant script using XmlBeans 2.0)
wlsdo.jar (from ALDSP 2.5)
xbean.jar
xqrl.jar
wlxbean.jar
ld-client.jar (from ALDSP 2.5)
I do the update in the way shown in attached java file.
After submit method call, I've got two copies of a new item added in the DB and also an exception that is shown in attached log-file.
What is the possible cause of this issue?
I use MySQL DBMS version 5.0.45.
I've also tried MS SQL 2005 but it simply had the same results.
DSP audit log is also attached.
Thank you in advance!
Best Regards,
Vitalii Tiutiunnyk

The problem is that your client is WLS server, and WLS server has network class loading disable (for security), and the result from the call requires a class that is not on the client. The call succeeds, but the the network class load for the result fails, and the WLS 9.2 framework (incorrectly) retries the call (and you get either a duplicate key exception or a second row inserted). Putting the server jar in the client classpath solves the problem.
If you wanted more information or help, you can contact BEA Customer Support and tell them it is regarding the CR I mentioned.

WebLogic Server 6.1:Incompatible service packs in CLASSPATH

Hi,
When I tried to start weblogic 6.1,I got the following exception.Please let me know,how to go ahead.
The WebLogic Server did not start up properly.
Exception raised: weblogic.common.internal.VersioningError: Incompatible service
packs in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP1 09/18/2001 14:28:44
#138716 , 6.1.1.0) not compatible with (BEA Systems, WebLogic XML Module 6.1 SP4
11/08/2002 22:04:40 #221641 , 6.1.4.0)
weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPAT
H: (BEA Systems, WebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716 , 6.1.1.0)
not compatible with (BEA Systems, WebLogic XML Module 6.1 SP4 11/08/2002 22:04
:40 #221641 , 6.1.4.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:
126)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:58)
at weblogic.version.<clinit>(version.java:18)
at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:277)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:340)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Edited by: user13282066 on Jul 29, 2010 4:37 AM

It looks like you are mixing SP1 and SP4 components in the server classpath.
Leaving aside the issue of supporting WL 6.1 ( nearly 10 years old! ), you should look at the classpath which will be listed in the server's log file when it starts up.
If this error has just recently started, has there been a modification to the startup scripts, or has there been a new patch installed?

Error Starting Weblogic Server as a Win2K service

Hi
I am unable to start Weblogic Server 6.1 as a Windows 2000 Server
service. Installation as NT service is successful and I used the password as
"weblogic" for the system user. But then when I try to start the service it gives
the following error complaining about incorrect password for the system user.
####<Sep 11, 2002 11:39:11 AM EDT> <Info> <Logging> <LDSERV10> <myserver> <main>
<> <> <000000> <FileLogger Opened.>
####<Sep 11, 2002 11:39:13 AM EDT> <Error> <Security> <LDSERV10> <myserver> <main>
<> <> <090052> <Server installed as NT Service with incorrect password for user
system.>
####<Sep 11, 2002 11:39:13 AM EDT> <Emergency> <Server> <LDSERV10> <myserver>
<main> <> <> <000000> <Unable to initialize the server: 'Fatal initialization
exception
Throwable: java.lang.SecurityException: Authentication for user system denied;
contact your administrator to correct NT Service attributes
java.lang.SecurityException: Authentication for user system denied; contact your
administrator to correct NT Service attributes
     at weblogic.security.SecurityService.initializeSuid(SecurityService.java:308)
     at weblogic.security.SecurityService.initialize(SecurityService.java:118)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
     at weblogic.Server.main(Server.java:35)
'>
Please, any help is gratly appriciated.
Thanks
Babu

"Babu Arumugam" <[email protected]> wrote:
>
Hi
I forgot to add in my prevoius msg that I am able to start the weblogic
server
from the cmd propt with out any error. The problem is only when I try
to start
it as a windows service .
Thanks
babu
Have you resolved this yet?
I had the same problem, and read that if I add the
"-password <password>" argument to the "beasvc.exe" command
in the "intallNtService.cmd" script, the problem was resolved.
To do this, you will have to use the "uninstallNtServer.cmd"
script to uninstall the service, edit the install script to
add the "-password <password>" argument to the beasvc.exe
command, then run the "installNtService.cmd" script to install
the service.
For me, it now works.
Good luck.

How can I tell my current Weblogic server version and Service pack

Hello,
I was wondering how can I tell what my current
weblogic server version is and what service pack
it is at.
Thanks.

use 'java weblogic.version'
ensure weblogic.jar is in the classpath

Weblogic Server does not show managed server started when I used the Windows service to start it.

I created a windows service to start a managed server and the services was created successfully and stated. WHen I go to the Weblogic Server Admn console, the server is still showing shutdown. Whenm I try to start it, it returns with error that the the service is not able to start. Has anyone ran into anything similar. I am running on Windows Server 2008R2 and running Weblogic Server 10.3.6 and Fusion Middleware 11.1.6.
C

Hi,
For starting managed server as windows service there is no need of nodemanager .
Please follow the steps given in the below doc:
How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
Thanks,
Sharmela

Weblogic Server 6.1 as an NT service - (post-install)

Similar Messages

Maybe you are looking for