Resetting targets WLS 6.1

I have a problem that occurs sproadically. When I restart the server (6.1) I
have to re-target everything that has been deployed including the default
web app, connection pools, datasource and ejbs.
How do I ensure that the target server for these deployments is selected on
start up? (I only have one server instance running).

If you have already targetted the applications to the managed server, they
should be automatically deployed when you restart the managed server. There
would be no need to re-target them.
Could you please check the config.xml and verify that the Targets attribute for
the concerned applications point correctly to the managed server.
Also, does the managed server communicate with the Admin server when it is
starting up. I would suggest you to set the Logging to <Info> for the managed
server to see if any other exceptions are thrown while starting up.
Mihir
bh wrote:
I have a problem that occurs sproadically. When I restart the server (6.1) I
have to re-target everything that has been deployed including the default
web app, connection pools, datasource and ejbs.
How do I ensure that the target server for these deployments is selected on
start up? (I only have one server instance running).

Similar Messages

Uata: WARNING: timeout: reset target chno = 0 targ = 0

Hi ,
Any idea what is the cause of the alert I usaully get this wen wen explorer run on server , it is
5.9 Generic_118558-36 sun4u sparc SUNW,Sun-Fire-V240
Thxs
TaD

user13112189 wrote:
it shows that your primary Disk was having issue with bus and mirroring was not properly worked during this period which cause for server become non-responsive.
Jun 2 20:07:59 uata: [ID 464412 kern.warning] WARNING: timeout: reset target chno = 0 targ = 0
timeout: <message> chno =<number> target=<number>
A timeout occured because of <message> on device (target=<number>) on channel (chno =<number). Where <message> could be either early abort, early timeout, abort request, abort device, reset target or reset bus
ata_controller - set features failed
Indicates a fatal problem with the drive; features could not be set.
First workaround is to reset the server.....
-Ravi
.Please review the first response in this thread.
The only uATA device in a Sunfire V210 chassis is the optical drive.
The hard drives are SCSI.
Here's a link to a non-Oracle web site that has an archived version of the Sun System Handbook,
showing the specifications of that model system
Sunfire V210 Specifications at the SunShack SSH Archive
The quoted errors are likely bogus and not relevant because the optical drive was probably empty, thus no readable media.
The owner of that system will have to go to the box and begin normal "Troubleshooting 101".

Failed to reset target mailbox

Hello, moving mailboxes to a 2010 server to another one in a different forest, for some mailboxes gives " completed with warning" with log below. Some mailboxes move complete with success. Need a clean-mailboxdatabase to be able to access
the mailboxes with warning. What could be the cause ? Thanks
29/07/2014 13:08:12 [CASHUB01] Failed to reset the target mailbox after the move. Attempt 2/2.
Error details: MapiExceptionUnknownUser MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=196]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=184][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 64957   StoreEc: 0x80070057
    Lid: 25018
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.ExRpcConnection.OpenMsgStore(OpenStoreFlag storeFlags, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, MapiStore msgStorePrivate, String& correctServerDn, ClientIdentityInfo clientIdentityAs, String userDnAs, String applicationId,
CultureInfo cultureInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId, TimeSpan connectionTimeout)
   at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.CreateStoreConnection(String serverLegDN, String serverFQDN, OpenStoreFlag additionalOpenStoreFlags, MailboxConnectFlags mailboxConnectFlags)
   at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect(MailboxConnectFlags connectFlags)
   at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass19.<Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect>b__18()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect(MailboxConnectFlags connectFlags)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass65.<PostMoveCleanupTargetMailbox>b__63()
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
29/07/2014 13:08:12 [CASHUB01] Request is complete.

Hi,
Based on the description, the mailboxes moved successfully with warning seems normal, is it right?
What's your Exchange version?
I searched and found that the issue you experienced with moving mailbox is a known issue in Exchange 2010 SP2 RU3. I recommend you install the latest rollups.
If your Exchange version is Exchange 2010 SP3 or later, please check if there is any issue about AD replication. By default, moving mailbox in the same site, the homeMDB attribute change will be replicated to all DCs immediately. But the inter-site is 15
minutes.
If the issue persists, please check if there is any related events in the application log.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

How to reset (target) Windows Backup

If I setup a brand new 2012 R2 server and setup a Backup Schedule it all works fine. As long as I NEVER touch it.
On one machine I changed the target to a better location.
The whole backup seems to be at the new target, I can mount the virtual drives and see everything.
But if I point the Restore wizard at it, it sees NOTHING. No backup found.
If I point it at the original target it's fine.
How do you "RESET" it.

Hi,
How do you change the backup target?
In Windows Server Backup we have 3 options "keep current backup destination", "add more backup destination" and "remove current backup destination". In my test I added a new destination and removed the old destination, after performing a backup, all backups
still exist in choosing Recover - "This Server" - even the restore points in the old location I removed.
If you have any feedback on our support, please send to [email protected]

Resetting targets again

I submitted this problem a couple of months ago.
My difficulty is that when I start the Weblogic server (I only have one - so
I understand that it starts as admin server) the targets for my deployments
don't 'take'.
I have to start the admin console and reset the targets for connection pools
, ejb's, web apps .... everything.
The config.xml shows the attribute targets with the correct value. No
exceptions are thrown on startup. No exceptions appear in the wl-domain log
My domain and server name are the same does this present a problem?
As I said I had this problem before and it went away, except that
periodically on server restart the targetting failed. I would just shut down
and restart and everything would be fine. This morning I reinstalled the
server and the targets failed every time except once - even though there
were no changes to configuration.
Thanks for any help.

I change the name of the domain so that it is different from the server and
that seems to have solved the problem.
"bh" <[email protected]> wrote in message
news:[email protected]..
I submitted this problem a couple of months ago.
My difficulty is that when I start the Weblogic server (I only have one -so
I understand that it starts as admin server) the targets for mydeployments
don't 'take'.
I have to start the admin console and reset the targets for connectionpools
, ejb's, web apps .... everything.
The config.xml shows the attribute targets with the correct value. No
exceptions are thrown on startup. No exceptions appear in the wl-domainlog
>
My domain and server name are the same does this present a problem?
As I said I had this problem before and it went away, except that
periodically on server restart the targetting failed. I would just shutdown
and restart and everything would be fine. This morning I reinstalled the
server and the targets failed every time except once - even though there
were no changes to configuration.
Thanks for any help.

How do I get a modorator to reset my target SNR

At approx 11.30 on 3.5.11 my line continuously dropped and re-established connection for about 20-30 mins (each time synchronising at circa 4800kbps and SNR of 6.0).
By 5.5.11, the (target) SNR had risen to 9db and the line was synching between 3700 and 4200kbps.
On Saturday 7.5.11 I spoke to customer support who reset target snr margin to 6 and line synched at >4800kbps. Unfortunately, in the evening, target snr margin was at 12db with synch between 2800-3500kbps. It has been like this ever since.
I have asked for target snr to be reset to 6db almost every day since then with assurances that it will happen. It hasn't (even when put through to UK help team last night). My line has operated perfectly well for the past 3 years at target snr of 6db. I know both from previous dealings with BT and from these community support forums that BT Wholesale can manually change target SNR to the default of 6th either by a team leader talking to them or a forum moderator instigating the change.
Unless this change is made, I will not achieve the synch speed I know is possible. How do I get a modorator to reset my target SNR back to 6db?

welcome to the forum
have you found the cause of all your reset problems which resulted in your increase in noise margin and reduction in speed? If you get the noise margin dropped to normal 6 and the noise problem is still there then in a few days maybe even sooner you will be back with a noise problem of 12 again
has you connection been stable with noise margin of 12 or has it still been resetting.
you can email the mods by completing the form http://bt.custhelp.com/app/contact_email/c/4951
may take a few days for the mods to get back to you.
it would help your case if you psot you adsl stats showiing your stable connection
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Connecting 2 WLS 7 servers via the Messaging Bridge

Hi,
          I am trying to use the messaging bridge to post messages received on a
          source JMS queue running in one WLS instance to a destination queue running
          on another target WLS instance. I have followed the instructions in the
          admin guide and performed the following:
          - defined in the source WLS instance 2 JMS bridge destinations - one for the
          source queue and one for the target queue
          - defined the bridge between the 2 destination, using the jms-xa-adp.rar
          - deployed the jmx-xa-adp.rar adapter to the source WLS instance
          - enabled the XA connection factory (had to define a new connection factory
          to do this)
          - made sure that both WLS instances have the system user configured with the
          same password
          When the source WLS instance starts up, the following is logged to the
          console:
          weblogic.jms.common.JMSException: Connection not found
          at
          weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java
          :134)
          at
          weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:592)
          at
          weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
          at
          weblogic.jms.client.JMSConnection.createSession(JMSConnection.java:368)
          at
          weblogic.jms.client.JMSXAConnection.createXAQueueSession(JMSXAConnection.jav
          a:75)
          at
          weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:
          257)
          at
          weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:215)
          at
          weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMS
          ManagedConnectionFactory.java:1
          at
          weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
          ol.java:1002)
          at
          weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
          ol.java:1777)
          at
          weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
          ctionPoolManager.java:190)
          at
          weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
          ConnectionManagerImpl.java:25)
          at
          weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
          nectionFactory.java:126)
          at
          weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
          java:753)
          at
          weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:91
          9)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          and any messages sent to the source queue just sit there.
          What might I be missing? Am I correct that the configuration of the bridge
          and destinations takes place at the source WLS instance (as this is posting
          the messages to the target WLS) - the documentation seems to me a bit
          ambiguous in this regard.
          Thanks,
          Stanley.


I am afraid that you'll have to enable security interoperability for
          the bridge to work across two domains. Making the password for
          system user is not enough. You have to disable generated credential
          for both domains. For details, please look at the following link:
          http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html#1078380
          Please also note that this requirement has been removed in 8.1 release and
          7.0SP3.
          Thanks
          Dongbo
          Stanley Beamish wrote:
          > "Dongbo Xiao" <[email protected]> wrote in message
          > news:[email protected]...
          > > I suspect that the two WebLogic servers have the same name.
          > > There are some naming restrictions in the WLS configuration.
          > > Please take a look at the following link.
          > > http://e-docs.bea.com/wls/docs70/adminguide/msgbridge.html#1076982
          > >
          > > Dongbo
          >
          > OK, I've changed the name of one of the servers and I can get further. But
          > now I get the following exception on the server that hosts the bridge,
          > relating to permissions. Both servers use the same system password.
          >
          > Thanks,
          > SB
          >
          > java.lang.SecurityException: Invalid Subject: principals=[system,
          > Administrators, Operators, Monitors, Deployers]
          > at
          > weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager
          > .java:993)
          > at
          > weblogic.security.service.RoleManager.getRoles(RoleManager.java:277)
          > at
          > weblogic.security.service.AuthorizationManager.isAccessAllowed(Authorization
          > Manager.java:589)
          > at weblogic.jms.JMSService.checkPermission(JMSService.java:1064)
          > at weblogic.jms.JMSService.checkRecvPermission(JMSService.java:1076)
          > at
          > weblogic.jms.frontend.FESession.consumerCreate(FESession.java:944)
          > at weblogic.jms.frontend.FESession.invoke(FESession.java:2252)
          > at
          > weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
          > at
          > weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
          > at
          > weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1592)
          > at
          > weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1452)
          > at
          > weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1302)
          > at
          > weblogic.jms.adapter.JMSBaseConnection.setMessageListenerInternal(JMSBaseCon
          > nection.java:931)
          > at
          > weblogic.jms.adapter.JMSBaseConnection.setMessageListener(JMSBaseConnection.
          > java:885)
          > at
          > weblogic.jms.adapter.JMSConnectionHandle.setMessageListener(JMSConnectionHan
          > dle.java:121)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at
          > weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrappe
          > r.java:101)
          > at $Proxy103.setMessageListener(Unknown Source)
          > at
          > weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge
          > .java:862)
          > at
          > weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:94
          > 2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          > >
          > > Stanley Beamish wrote:
          > >
          > > > Hi,
          > > >
          > > > I am trying to use the messaging bridge to post messages received on a
          > > > source JMS queue running in one WLS instance to a destination queue
          > running
          > > > on another target WLS instance. I have followed the instructions in the
          > > > admin guide and performed the following:
          > > >
          > > > - defined in the source WLS instance 2 JMS bridge destinations - one for
          > the
          > > > source queue and one for the target queue
          > > > - defined the bridge between the 2 destination, using the jms-xa-adp.rar
          > > > - deployed the jmx-xa-adp.rar adapter to the source WLS instance
          > > > - enabled the XA connection factory (had to define a new connection
          > factory
          > > > to do this)
          > > > - made sure that both WLS instances have the system user configured with
          > the
          > > > same password
          > > >
          > > > When the source WLS instance starts up, the following is logged to the
          > > > console:
          > > >
          > > > weblogic.jms.common.JMSException: Connection not found
          > > > at
          > > >
          > weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java
          > > > :134)
          > > > at
          > > >
          > weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:592)
          > > > at
          > > >
          > weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
          > > > at
          > > > weblogic.jms.client.JMSConnection.createSession(JMSConnection.java:368)
          > > > at
          > > >
          > weblogic.jms.client.JMSXAConnection.createXAQueueSession(JMSXAConnection.jav
          > > > a:75)
          > > > at
          > > >
          > weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:
          > > > 257)
          > > > at
          > > > weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:215)
          > > > at
          > > >
          > weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMS
          > > > ManagedConnectionFactory.java:1
          > > > )
          > > > at
          > > >
          > weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
          > > > ol.java:1002)
          > > > at
          > > >
          > weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
          > > > ol.java:1777)
          > > > at
          > > >
          > weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
          > > > ctionPoolManager.java:190)
          > > > at
          > > >
          > weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
          > > > ConnectionManagerImpl.java:25)
          > > > at
          > > >
          > weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
          > > > nectionFactory.java:126)
          > > > at
          > > >
          > weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
          > > > java:753)
          > > > at
          > > >
          > weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:91
          > > > 9)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          > > >
          > > > and any messages sent to the source queue just sit there.
          > > >
          > > > What might I be missing? Am I correct that the configuration of the
          > bridge
          > > > and destinations takes place at the source WLS instance (as this is
          > posting
          > > > the messages to the target WLS) - the documentation seems to me a bit
          > > > ambiguous in this regard.
          > > >
          > > > Thanks,
          > > > Stanley.
          > >
          [att1.html]

EJB Deployment Descriptors not deploying to WLS

Hi,
We're using Eclipse 3.4.1 with the OEPE to target WLS 10.3 with Java 6/JEE 1.4 on a Windows XP Professional development machine.
We have an EJB 2.1 project as part of a larger EAR. The beans (all stateless session beans) and associated interfaces and deployment descriptors within are maintained manually for internal reasons; we do not rely on EJBGen or XDoclet or anything like that to manage these. We are NOT using any annotations in these EJBs, as is the default when you create a bean. Instead we rely on weblogic-ejb-jar.xml and ejb-jar.xml.
We're having an issue where deploying to the local Weblogic server instance fails with the following error displaying in the Eclipse console:
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxxxxx'.>
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxxxxxxEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:199)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     Truncated. see log file for complete stacktrace
We DO have multiple beans defined, but it seems that WLS just isn't aware of them due to the lack of a deployment descriptor. It appears that Eclipse/OEPE is not copying the ejb-jar.xml and weblogic-ejb-jar.xml files to the build directory when the project is build:
xxxxxEJB
|-- ejbModule
|.....|-- META-INF
|.....|.....|-- ejb-jar.xml
|.....|.....|-- MANIFEST.MF
|.....|.....|-- weblogic-ejb-jar.xml
|.....|-- com (etc., .java files)
|-- build
......|-- classes
............|-- META-INF
............|......|-- MANIFEST.MF
............|-- com (etc, .class files)
Other notes:
- Cleaning the project does not help.
- Starting a new workspace does not help.
- It works under Eclipse 3.3.2 with the Europa version of OEPE.
- Explicitly exporting an EJB Jar file DOES include the two deployment descriptors (just not deploying to the embedded test server we've defined in our Servers view)
Any ideas? This seems like either a bug in the OEPE, or maybe WTP.

Yes, I have a simple EJB2.1 project with hand-crafted EJB remote/home interfaces/classes and deployment descriptors. Also tried Clean/Rebuild and manually delete
files under /build/classes.
Here are my descriptors files:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
     <display-name>TestEJB</display-name>
<enterprise-beans>
<session>
<display-name>HelloSessioin</display-name>
<ejb-name>HelloSession</ejb-name>
<home>sessions.HelloSessionHome</home>
<remote>sessions.HelloSession</remote>
<ejb-class>sessions.HelloSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<security-identity>
<use-caller-identity/>
</security-identity>
</session>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloSession</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<jndi-name>ejb.HelloSessionRemoteHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Did you check if there is any error/warning in Error Log view?

IDE/ATA + DMA + Resets

Hi,
I used to have problem with my Intel workstation when I was running Solaris 8 with ata-dma enabled. The problems disapeared after I upgraded to Solaris 9.
I've been using Solaris 10 b72 for about a month and the problems have came back on the same hardware.
When accessing files from two disks at the same time I get error messages like these in the syslog:
-- cut --
Jan 8 22:49:17 sara scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@11,1/ide@1 (ata1):
Jan 8 22:49:17 sara timeout: abort request, target=0 lun=0
Jan 8 22:49:17 sara scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@11,1/ide@1 (ata1):
Jan 8 22:49:17 sara timeout: reset target, target=0 lun=0
Jan 8 22:49:17 sara scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@11,1/ide@1 (ata1):
Jan 8 22:49:17 sara timeout: reset bus, target=0 lun=0
Jan 8 22:49:18 sara scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@11,1/ide@1 (ata1):
Jan 8 22:49:18 sara.homeunix.net timeout: early timeout, target=0 lun=0
Jan 8 22:49:18 sara gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@11,1/ide@1/cmdk@0,0 (Disk2):
Jan 8 22:49:18 sara Error for command 'read sector' Error Level: Informational
-- cut --
When I disable ata-dma-enable using eeprom the problems disapear but I get transfer rates of approx 4mb/s.
When booting up the OS identifies the disks:
-- cut --
Jan 8 22:37:11 sara pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 0
Jan 8 22:37:11 sara last message repeated 1 time
Jan 8 22:37:11 sara genunix: [ID 640982 kern.info] IDE device at targ 0, lun 0 lastlun 0x0
Jan 8 22:37:11 sara genunix: [ID 846691 kern.info] model ST340014A
Jan 8 22:37:11 sara genunix: [ID 479077 kern.info] ATA/ATAPI-6 supported, majver 0x7e minver 0x1b
Jan 8 22:37:11 sara.homeunix.net genunix: [ID 228648 kern.info] ata_set_feature: (0x66,0x0) failed
Jan 8 22:37:11 sara genunix: [ID 773945 kern.info] UltraDMA mode 5 selected
Jan 8 22:37:11 sara genunix: [ID 640982 kern.info] IDE device at targ 1, lun 0 lastlun 0x0
Jan 8 22:37:11 sara genunix: [ID 846691 kern.info] model ST320410A
Jan 8 22:37:11 sara genunix: [ID 479077 kern.info] ATA/ATAPI-6 supported, majver 0x7e minver 0x0
Jan 8 22:37:11 sara genunix: [ID 228648 kern.info] ata_set_feature: (0x66,0x0) failed
Jan 8 22:37:11 sara genunix: [ID 773945 kern.info] UltraDMA mode 5 selected
-- cut --
The system is using a AMI bios and the motherboard chipset is VIA KT133.
The system consists of 3 Seagate disks, they are properly jumpered as master+slave + master. I've set up the BIOS to auto-detect the disks.
Could anyone confirm it this is a bug or if Sun has removed support for my motherboard chipset... or any pointers that could assist me in getting my system functional again.
Many thanks,
Martin Andersson

As far as I can see the difference between those drives is slim 12.5mm or ultra slim 9.5mm height. (Are you sure there not Hitachi?) I'm 95% sure the TiBooks will take the 12.5mm drives.I recommend looking in Apple System Profile to see exactly what model you currently have installed and then find one with the same dimensions.
hth
mrtotes
Deal Time
Deal Time 7k60
Toshiba Laptop HDD

V240 - removed optical drive, now having constant HBA (ata controller)reset

Hi there,
I have 2 Fire v240's - and only one working DVD optical drive which I move between them.. Running Solaris 05/09, whichever machine doesnt have the optical drive physically installed, goes through a continuous routine of resetting hba and trying to re-sync with it..
--start messages snippet
Feb 10 12:40:07 hosta uata: [ID 464412 kern.warning] WARNING: timeout: reset target chno = 0 targ = 0
Feb 10 12:40:12 hosta uata: [ID 606412 kern.warning] WARNING: timeout: reset bus chno = 0 targ = 0
Feb 10 12:40:32 hosta uata: [ID 252109 kern.warning] WARNING: ata_controller - Set features failed
Feb 10 12:40:32 hosta uata: [ID 859416 kern.info] ghd_timer_newstate: HBA reset failed hba 0x60011149800 gcmdp 0x60016280c40 gtgtp 0x60011072b40
---end messages snippet (repeated approx every 2 minutes)
There is surely a way for me to disable the controller or advise Solaris to stop trying to talk to the missing hardware (DVD drive)?
Many thanks!
Hugo

Humm, can you see the DVD somehow in cfgadm -l or cfgadm -lv? If so you should be able to unconfigure or disconnect it from the OS :-)
.7/M.

Solaris 8 installation problem on Dell PowerEdge 500SC

Hi,
I am having TWO PROBLEMS installing Solaris 8 on Dell PowerEdge 500SC.
This hardware spec is:
Pentium-III at 1GHz
256MB 133MHz ECC SDRAM
20GB 7200RPM ATA100 EIDE hard drive (on integrated ATA-100 controller)
48X EIDE CD-ROM drive (on integrated ATA-100 controller)
Motherboard: unknown
more details: http://www.dell.com/us/en/esg/topics/esg_pedge_sc_towermain_servers_3_pedge_500sc.htm
FIRST PROBLEM is the following message was shown at the hardware probe.
WARNING: ACPI Tables not in Reclaim Memory
Warning: Resource Conflict - both devices are added
NON-ACPI device: PNP0C01
Port: C00-C01, C06-C08, C14, C50-C52, C6C-C6F,
CD6-CD7
F50-F57
ACPI device: PNP0C01
Port 814-85B, 580-58F, C00-CD7, F50-F58
At this time, I was using "Solaris 8 (Intel Platform Edition) 10/01" released version.
I am not sure what this means, but it was RESOLVED with using newer "x86 DCA boot diskette (Patch-ID# 110930-05)".
But, the SECOND REAL PROBLEM is another one. It just happens booting the kernel after the hardware probe. I get the following messages about 2 minutes later, after beginning to load kernel.
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: abort request, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: about device, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: reset target, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: reset bus, target=0 lun=0
After another 1 or 2 minutes I get more error and the system reboots.
Please give me any suggestion or advice!
Thanks.
Kazuyoshi

I've been having the exact same problems on a PowerEdge 500SC. I have managed to get Solaris up and running on the machine, however. I booted the DCA from the floppy disk and installed from the CD-ROM. When the DCA is ready to scan for devices I use the "Specific Scan" option to tell it to look for specific devices. I tell it to scan for all devices in the listing and in doing so the DCA finds ISA-based IDE controllers. After it provides a listing of the devices it found I use the "Device Tasks" option and the "View/Edit Devices" menu item then delete the Bus Mastering IDE controller device. Once the screen comes up to ask for a boot device, the drives will show up as on the ISA controllers.
I have to go through this process every time I boot the machine but I am able to make the system run at least.
I haven't figured out the ACPI problem, yet.
Regards,
Doug

Error in running a simple JSF app developed in Jdeveloper over weblogic

I have a developed a simple JSF application using Jdeveloper 11g.
To this application i have added a webservice proxy which generates the proxy client which communicates with the peoplesoft webservice.
when i run the standalone proxy class, it is able to connect to the webservice and get the required data.
But as i deploy the whole JSF application (where the managed bean calls a method in the client) in Integrated weblogic server, i get an XMLStreamReaderException.
To debug this issue i deployed the war file in apache-tomcat6.0.26 with all the reqquired libraries in the Lib folder, it actually worked , my jsf application was able to get the data from the webservice.
This makes me think that there is some problem in the way Jdeveloper is packaging the application.I have added all the lib & jar through "libraries &classpath" setting on project properties.But i am sure there is some problem in this process.
I just need some help in understanding how to package an application,how to make sure all lib & jar are included in the war file??
Any help is appreciated.
The error i get in the weblogic is
com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
avax.faces.el.EvaluationException: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at javax.faces.component.UICommand.broadcast(UICommand.java:387)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227
thanks in advance
Ash

HI
First of all, how do you concluded that you're dealing with packaging problem?? It seems problem is in response from web service. The toolkit you have is not able to parse the soap response. Tomcat solves problem probably because of the different jars he has for web service client.
In either way, i have personally experienced problems with JD packaging (11g). The WAR created by JD was working well in embedded WLS shipped with JD, but when deployed to production WLS 10.3.1, i got a "IO exception; premature end of file". The only solution was to create a WAR by ant.
Here is ANT sample script for building java classes, packaging into war, deploying to WLS (for this last one, you need to reference external jar):
<target name="build">

<javac debug="true" debuglevel="${debuglevel}" source="${source_version}" target="${target_version}" destdir="${output.dir}">
<src path="${src.location}"/>
</javac>
</target>
     <target name="war" depends="build">
<delete file="${target_war_file}"/>
<war destfile="${target_war_file}" webxml="src/WEB-INF/web.xml" manifest="/src/META-INF/MANIFEST.MF" update="true">
<classes dir="${output.dir}"/>
<lib dir="${build_libs.location}">
<include name="**/*.jar"/>
</lib>

<zipfileset dir="${path.to.conf.folder}" prefix="WEB-INF">
<include name="adfc-config.xml"/>
<include name="trinidad-config.xml"/>
<include name="web.xml"/>
<include name="weblogic.xml"/>
</zipfileset>
</war>
</target>
     <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
<classpath>
<pathelement location="c:/oracle/wlserver_10.3/server/lib/weblogic.jar"/>
</classpath>
</taskdef>
<target name="deploy">
<wldeploy action="deploy" verbose="true" upload="true" remote="true" debug="true" name="${wls.app.name}" user="${wls.user}" password="${wls.password}" adminurl="${wls.admin.url}"
targets="${wls.targets}" securitymodel="CustomRoles" source="${target_war_file}" nostage="false"/>
</target>
<target name="undeploy">
<wldeploy action="undeploy" verbose="true" name="${wls.app.name}" user="${wls.user}" password="${wls.password}" adminurl="${wls.admin.url}" targets="${wls.targets}" failonerror="false"/>
</target>

Regards

Upgrading Weblogic server to move from jdeveloper 11.1.1.1.0 to 11.1.1.4.0

Hello, I would need clear direction to what I should do to upgrade my target weblogic server when I move my development environment from jdeveloper 11.1.1.1.0 to 11.1.1.4.0
Initial ADF project was developed with jdeveloper 11.1.1.1.0 and deployed on a WLS 10.3.0
Now we are upgrating the application and we decided to move the project to jdeveloper 11.1.1.1.4
I need help on what I should upgrade on the target WLS server.
How do we move from WLS 10.3.0 to WLS 10.3.4?
Is it a reinstall or a upgrade? How do we upgrade?
And what about just upgrating the ADF run time? Is it the way to go?
At following link we see
http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html there is a Application development runtime is it the runtime that we install on the server or not?
I am confused if the ADF run time is tied with the WLS version or not, can someone give me a clear description of what is the ADF Runtime and how we upgrade it on the servers? Any Oracle documentation describing this process that I can provide to my server administrators?
At the end what is the best practice to upgrade the WLS servers when you would lilke to move like me from an older version of jdeveloper to a newer version. is there an Oracle document describing the steps to be done?
Thanks

I'll echo Timo's question - why upgrade to 11.1.1.4 and not to the latest and greatest 11.1.1.6 (released yesterday)?
Upgrading to an older version basically means that you are setting yourself for another upgrade later on - so why not enjoy all the bug fixes and new features of the newer versions?
In terms of the upgrade process - if you look in the documentation tab of JDeveloper you'll see the book "Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF" which gives the steps you can follow.
For 11.1.1.6 the book is here:
http://docs.oracle.com/cd/E23943_01/upgrade.1111/e10127/toc.htm
In the same documentation tab you'll find the certification matrix that explains which ADF version works with which WLS version:
http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html

Solaris 10 instalatot can't read or write my UDMA mode 2 HDDs

I have TX98-3D motherboard and two 2GBs HDDs (primary master, primary slave)
During startup (after "Configuring devices" text) it raises multiple warnings for both disks (/pci@0,0/pci-ide@7,1/ide@0 (ata0) for one of them) with texts like "timeout: abort request, target=1 lun=0","timeout: abort device, target=1 lun=0", "timeout: reset target, target=1 lun=0", "timeout: reset bus, target=1 lun=0".
This block of WARNING is followed by:
"WARNING: /pci@0,0/pci-ide@7,1/ide@0/cmdk@1,0 (Disk1):
Error for command 'read sector' Error Level: Informational
Sense Key: aborted command
Vendor 'Gen-ATA ' error code: 0x3
few seconds before this message HDD LED starts to shine permanently.
After manual system layout (auto not works - not enough space) it displays something
like "cannot create partion" or "disk not writtable"?
Can it be solved by adding old ISA expansion card with IDE controller and attaching disks to it?
Please help me.

AAhhhh.....
Ye Olde socket-7 TX98 board...
I remember it well, back in the day.
Mine was an AMD K6 @ 233MHz that I overclocked to 300MHz
I fear that hardware is just a bit too old for Solaris 10.
For example, Sol-10 really doesn't like ANYTHING on the ISA expansion bus.
The OS will also need more RAM than you can install to that board.
You may need to think about finding something newer.
I'm currently running Sol-10 on an Intel 440BX slot-1 P-III.

Failover is work, but Session replication doesn't work!

Dear all,
          My Cluster can failover, but can't session replicate....
          I start up the 2 WLS 6.0 and the Web Server, then I visit
          http://web_server_ip/myWebApp/SessionServlet serveral times, then the
          counter variable in the session raise up, then I down the "target" WLS, then
          I try http://web_server_ip/myWebApp/SessionServlet now, I can call but the
          counter restart.... so the session seems not yet replicated. what I can
          do...?!
          My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using libproxy.so
          with the cluster setting, and use 2 WLS 6.0 (both are running in 7001,7002)
          as the Application Server Cluster (WLCluster). one WLS is on Unix Machine
          and the other in on a NT. I set the 2 WLSs: the Primary Group is
          "WL_rep_group1", and set the secondary is "WL_rep_group2".
          Deployment: I deploy the application "myWebApp" (.war) on the servers unix
          and nt, adn also deploy to the cluster WLCluster.
          I deploy the examplesWebApp to my created domain "demo", and modify the
          weblogic.xml:
          <weblogic-web-app>
          <session-descriptor>
          <session-param>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          <jsp-descriptor>
          <jsp-param>
          <param-name>
          pageCheckSeconds
          </param-name>
          <param-value>
          1
          </param-value>
          </jsp-param>
          <jsp-param>
          <param-name>
          verbose
          </param-name>
          <param-value>
          true
          </param-value>
          </jsp-param>
          </jsp-descriptor>
          </weblogic-web-app>
          so ... anything I did wrong, so the WLS can't do Session replication??!!
          Please Help or Comment!
          Thanks in advance!
          with thanks,
          Alex Wong


Dear Vinod and Kevin,
          Some more information that I think it may help.
          First, I want to correct 1 point in my previous message, the Replication
          Group is "WLRepGroup1" and the Preferred Secondary Group is "WLRepGroup2"
          for the 2 machine WLSs.
          Second, I found that the Multicast Communication is not functioning becoz
          the switch of my office block the 224.0.0.1's communication, so now I added
          a hub for this 2 machine, as a result the multicast is wokring... at least
          pass the java utils.MulticastTest....
          Thrid, after the mutlicast work, I try the SessionServlet, it is working at
          beginning... but after some more clicks, one server will cause the following
          error (this time crash on x.y.z.b--NT machine)....
          -------- (a long list, the IPs are replaced: x.y.z.a UNIX machine, x.y.z.b
          NT machine, x.y.z.c My PC)
          Screen caption on demo>Servers>wlserver2 (monitoring> cluster)
          Unexpected Error
          Connected to x.y.z.a:7001 Active Domain: demo Jun 11, 2001 5:06:23 PM
          GMT+08:00
          An unexpected error was encountered in processing your request.
          Exception
          java.lang.NullPointerException
          <>
          Current Date
          Mon Jun 11 17:06:23 GMT+08:00 2001
          Console Release Build
          6.0 Service Pack 2
          Console Build
          6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          Server Release Build
          6.0 Service Pack 2
          Server Build
          6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          All Server Product Versions
          WebLogic Server Build: 6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          WebLogic XML Module: 6.0 Service Pack 2 05/24/2001 12:34:27 #117037
          Request Info
          Protocol: HTTP/1.1
          ServerName: x.y.z.a
          ServerPort: 7001
          Secure: false
          ContextPath: /console
          ServletPath: /panels/mbean/Server.jsp
          QueryString:
          mbean=demo%3AName%3Dwlserver2%2CType%3DServer
          PathInfo: null
          PathTranslated: null
          RequestURI: /console/panels/mbean/Server.jsp
          AuthType: null
          ContentType: null
          CharacterEncoding: null
          Locale: zh_TW
          Method: GET
          Session:
          weblogic.servlet.internal.session.MemorySessionData@661950
          RequestedSessionId:
          OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX/console
          RequestedSessionIdFromCookie: true
          RequestedSessionIdFromURL: false
          UserPrincipal: system
          RemoteUser: system
          RemoteAddr: x.y.z.c
          RemoteHost: x.y.z.c
          Parameters
          mbean = demo:Name=wlserver2,Type=Server
          Attributes
          console.original./console/panels/mbean/Server.jsp.ContextPath = /console
          console.original./console/panels/mbean/Server.jsp.Method = GET
          console.original./console/panels/mbean/Server.jsp.QueryString =
          mbean=demo%3AName%3Dwlserver2%2CType%3DServer
          console.original./console/panels/mbean/Server.jsp.RemoteUser = system
          console.original./console/panels/mbean/Server.jsp.RequestURI =
          /console/panels/mbean/Server.jsp
          console.original./console/panels/mbean/Server.jsp.ServletPath =
          /panels/mbean/Server.jsp
          console.preferences.ContextKey =
          /panels/mbean/Server.jsp
          javax.servlet.include.context_path = /console
          javax.servlet.include.request_uri =
          /console/common/requestinfo.jsp
          javax.servlet.include.servlet_path =
          /common/requestinfo.jsp
          javax.servlet.jsp.jspException =
          java.lang.NullPointerException
          weblogic.httpd.user = system
          weblogic.management.console.tags.ContentTag =
          java.lang.Object@545f89
          weblogic.management.console.tags.HeaderTag =
          java.lang.Object@4c5c6c
          weblogic.management.console.tags.TabbedDialogTag =
          java.lang.Object@7eafc
          Headers
          Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
          Accept-Encoding = gzip, deflate
          Accept-Language = zh-tw
          Connection = Keep-Alive
          Cookie =
          JSESSIONID=OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX!143710744761
          7668081!-896735123!7001!7002!NONE
          Host = x.y.z.a:7001
          User-Agent = Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
          BrowserInfo
          User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
          IE: true
          Netscape: false
          Supported: true
          JavscriptHrefs: false
          TableCellClick: true
          DocumentReloadedOnResize: false
          DropdownStretchable: true
          CellSpacingBlank: false
          EmptyCellBlank: false
          ImgOnclickSupported: true
          TableBorderFancy: true
          PartialToWideTables: false
          Server System Properties
          bea.home = /u0/weblogic
          file.encoding = ISO8859-1
          file.encoding.pkg = sun.io
          file.separator = /
          java.awt.fonts =
          java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
          java.awt.printerjob = sun.awt.motif.PSPrinterJob
          java.class.path =
          /u0/weblogic/wlserver6.0:/u0/weblogic/wlserver6.0/lib/weblogic_sp.jar:/u0/we
          blogic/wlserver6.0/lib/weblogic.jar:/opt/oracle/product/8.1.6/jdbc/lib/class
          es12.zip
          java.class.version = 47.0
          java.ext.dirs = /u0/weblogic/jdk130/jre/lib/ext
          java.home = /u0/weblogic/jdk130/jre
          java.io.tmpdir = /var/tmp/
          java.library.path =
          /u0/weblogic/jdk130/jre/bin/../lib/sparc/hotspot:/u0/weblogic/jdk130/jre/bin
          /../lib/sparc::/lib:/usr/local/easysoft/oob/client:/usr/local/easysoft/lib:/
          u0/weblogic/wlserver6.0/lib/solaris:/u0/weblogic/wlserver6.0/lib/solaris/oci
          816_8:/usr/lib
          java.naming.factory.initial =
          weblogic.jndi.WLInitialContextFactory
          java.naming.factory.url.pkgs = weblogic.jndi.factories
          java.protocol.handler.pkgs =
          weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|
          weblogic.net|weblogic.utils
          java.runtime.name = Java(TM) 2 Runtime Environment,
          Standard Edition
          java.runtime.version = 1.3.0
          java.security.policy =
          =/u0/weblogic/wlserver6.0/lib/weblogic.policy
          java.specification.name = Java Platform API Specification
          java.specification.vendor = Sun Microsystems Inc.
          java.specification.version = 1.3
          java.vendor = Sun Microsystems Inc.
          java.vendor.url = http://java.sun.com/
          java.vendor.url.bug =
          http://java.sun.com/cgi-bin/bugreport.cgi
          java.version = 1.3.0
          java.vm.info = mixed mode
          java.vm.name = Java HotSpot(TM) Client VM
          java.vm.specification.name = Java Virtual Machine
          Specification
          java.vm.specification.vendor = Sun Microsystems Inc.
          java.vm.specification.version = 1.0
          java.vm.vendor = Sun Microsystems Inc.
          java.vm.version = 1.3.0
          javax.rmi.CORBA.PortableRemoteObjectClass =
          weblogic.iiop.PortableRemoteObjectDelegateImpl
          javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
          javax.xml.parsers.DocumentBuilderFactory =
          weblogic.xml.jaxp.RegistryDocumentBuilderFactory
          javax.xml.parsers.SAXParserFactory =
          weblogic.xml.jaxp.RegistrySAXParserFactory
          jmx.implementation.name = JMX RI
          jmx.implementation.vendor = Sun Microsystems
          jmx.implementation.version = 1.0
          jmx.specification.name = Java Management Extensions
          jmx.specification.vendor = Sun Microsystems
          jmx.specification.version = 1.0 Final Release
          line.separator =
          os.arch = sparc
          os.name = SunOS
          os.version = 5.6
          path.separator = :
          sun.boot.class.path =
          /u0/weblogic/jdk130/jre/lib/rt.jar:/u0/weblogic/jdk130/jre/lib/i18n.jar:/u0/
          weblogic/jdk130/jre/lib/sunrsasign.jar:/u0/weblogic/jdk130/jre/classes
          sun.boot.library.path =
          /u0/weblogic/jdk130/jre/lib/sparc
          sun.cpu.endian = big
          sun.cpu.isalist = sparcv8plus+vis sparcv8plus
          sparcv8 sparcv8-fsmuld sparcv7 sparc
          sun.io.unicode.encoding = UnicodeBig
          user.dir = /u0/weblogic/wlserver6.0
          user.home = /
          user.language = en
          user.name = root
          user.region = US
          user.timezone = Asia/Hong_Kong
          weblogic.Domain = demo
          weblogic.Name = wlserver1
          weblogic.security.jaas.Configuration =
          weblogic.security.internal.ServerConfig
          weblogic.security.jaas.Policy =
          /u0/weblogic/wlserver6.0/lib/Server.policy
          ---------- End of the message -----------
          any comment?? is that I deploy on wlserver1, wlserver2, WLCluster cause
          error??!! anything I did wrong??!
          please help!! or Comment
          with thanks,
          Alex Wong
          "Alex Wong" <[email protected]> ¼¶¼g©ó¶l¥ó
          news:[email protected]...
          > Hi Vinod and Kevin,
          >
          > Thanks Vinod first, and after I try the session.getClass(), I get the
          > following output
          > class weblogic.servlet.internal.session.ReplicatedSessionData
          > I think that's means I am using "replicated" already, rite?!
          >
          > About the License, I cat the license.bea, there is a license to the
          > "In-memory Replication - Servlet" and "In-memory Replication - EJB",
          however
          > it is a eval license but seems not yet expired, so I don't think that is
          the
          > problem, rite?
          >
          > And a quick question, you tell me "your configuration looks ok" means the
          > H/W configuration, or the WLS configuration??!!
          > Maybe I tell you more about my WLS configuration, so that, you can
          > determinate where I go wrong. (thanks)
          >
          >
          > Vinod and Kevin
          > (Kevin, I am Alex Wong from ASL, if you have any comment, you can simply
          > reply my personal email, thx)
          >
          > Steps I did to create the domain, WLS and Cluster and deploy the .war
          > --- on Unix ---
          > I create a demo domain and wlserver1 using port 7001 and 7002 by the
          > installation program (ip x.y.z.a)
          > --- on NT ---
          > I create a demo domain and wlserver2 using port 7001 and 7002 by the
          > installation program (ip x.y.z.b)
          >
          > --- on Unix ---
          > start the wlserver1 with startWebLogic.sh
          >
          > --- My PC ---
          > go http://x.y.z.a:7001/console
          >
          > create one more server named "wlserver2" using port 7001 and 7002
          > create the cluster named "WLCluster" and fill the the cluster ip
          > "x.y.z.a:7001,x.y.z.b:7001"
          > fill the multi-cast ip 224.0.0.1
          > add the "wlserver1" and "wlserver2" to the "WLCluster"
          > stop the unix WLS
          > start the unix WLS with startWebLogic.sh
          >
          > --- on NT ---
          > start the WLS with startManagedWebLogic.sh wlserver2 http://x.y.z.a:7001
          >
          > --- on Unix ---
          > install the NES 3.6.3 and create a WEB server instance and modify the
          > obj.conf
          >
          > DETAIL
          > ----- start of the obj.conf -----
          > Init fn="load-modules" funcs="wl-proxy,wl-init"
          > shlib="/opt/nes/plugins/weblogic/libproxy.so"
          > Init fn="wl-init"
          > .
          > .
          > .
          > <Object name="weblogic" ppath="*">
          > Service fn=wl-proxy \
          > WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
          > </Object>
          >
          > <Object name=default>
          > *NameTrans ...
          > *NameTrans ...
          > *NameTrans ...
          > *NameTrans fn=document-root root="/opt/nes/docs"
          > Service method="(GET|HEAD|POST|PUT)" type=text/jsp fn=wl-proxy \
          > WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
          > .
          > .
          > .
          > </Object>
          >
          > <Object name=cgi>
          > .
          > .
          > .
          > </Object>
          > ----- End of the obj.conf ----- (I suppose will redirect all HTTP request
          to
          > WLS from NES)
          >
          > --- My PC ---
          > go http://x.y.z.a:7001/console
          > assign the DefaultWebApp_wlserver1 to wlserver1
          > assign the DefaultWebApp_wlserver2 to wlserver2
          > assign the console the wlserver1 only
          > assign the certificate to wlserver1, wlserver2, WLCluster
          > go SERVER-wlserver1 assign "WLRepGroup1" to Replication Group and
          Preferred
          > Secondary Group
          > go SERVER-wlserver2 assign "WLRepGroup1" to Replication Group and
          Preferred
          > Secondary Group
          >
          > --- on Unix ---
          > go to ./config/examples/applications/examplesWebApp/WEB-INF
          > modify the weblogic.xml
          > go to ./config/examples/applications/examplesWebApp
          > jar cvf myWebApp.war *
          > copy the myWebApp.war to ./config/demo/applications/.
          > and ftp myWebApp.war ro (NT)./config/demo/applicaitons/.
          >
          > --- My PC ---
          > And then now, I can visit http://x.y.z.a:7001/console
          > now I can configuration the myWebApp.
          > assign the myWebApp to wlserver1,wlserver2,WLCluster
          >
          > --- on Unix ---
          > stop the WLS and start with startWebLogic.sh
          >
          > --- on NT ---
          > stop the WLS and start with startManagedWebLogic.sh wlserevr2
          > http://x.y.z.a:7001
          >
          > --- My PC ---
          > visit http://x.y.z.a/myWebApp/SessionServlet (this time no port 7001,
          becoz
          > I want to use the NES web server to proxy the HTTP request)
          >
          > Finally... I can failover the SessionServlet, SnoopServlet and all the
          other
          > html, jsp, servlet, but seems can't load-balancing and Session
          Persistence.
          >
          > Is that anything I did wrong, please comment!
          >
          >
          > with thanks,
          >
          > Alex Wong
          >
          >
          >
          > "Vinod Mehra" <[email protected]> ¼¶¼g©ó¶l¥ó
          > news:[email protected]...
          > > Your configuration looks ok but I guess somehow your clustering is not
          > setup
          > > properly. Check if all the servers are listeniong on the same port and
          > part
          > > of
          > > the same cluster. Also check if you have clustering license.
          > >
          > > Make sure your sessions are of type : "replicated". For that print
          > > the value of session.getClass(), the name will give you an idea. Check
          > > your logs if you got any error message.
          > >
          > > --Vinod.
          > >
          > >
          > > "Alex Wong" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > Dear all,
          > > >
          > > > My Cluster can failover, but can't session replicate....
          > > >
          > > > I start up the 2 WLS 6.0 and the Web Server, then I visit
          > > > http://web_server_ip/myWebApp/SessionServlet serveral times, then the
          > > > counter variable in the session raise up, then I down the "target"
          WLS,
          > > then
          > > > I try http://web_server_ip/myWebApp/SessionServlet now, I can call but
          > the
          > > > counter restart.... so the session seems not yet replicated. what I
          can
          > > > do...?!
          > > >
          > > > My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using
          > > libproxy.so
          > > > with the cluster setting, and use 2 WLS 6.0 (both are running in
          > > 7001,7002)
          > > > as the Application Server Cluster (WLCluster). one WLS is on Unix
          > Machine
          > > > and the other in on a NT. I set the 2 WLSs: the Primary Group is
          > > > "WL_rep_group1", and set the secondary is "WL_rep_group2".
          > > >
          > > > Deployment: I deploy the application "myWebApp" (.war) on the servers
          > unix
          > > > and nt, adn also deploy to the cluster WLCluster.
          > > >
          > > > I deploy the examplesWebApp to my created domain "demo", and modify
          the
          > > > weblogic.xml:
          > > > -------------------
          > > > <weblogic-web-app>
          > > >
          > > > <session-descriptor>
          > > > <session-param>
          > > > <param-name>PersistentStoreType</param-name>
          > > > <param-value>replicated</param-value>
          > > > </session-param>
          > > > </session-descriptor>
          > > >
          > > > <jsp-descriptor>
          > > > <jsp-param>
          > > > <param-name>
          > > > pageCheckSeconds
          > > > </param-name>
          > > > <param-value>
          > > > 1
          > > > </param-value>
          > > > </jsp-param>
          > > > <jsp-param>
          > > > <param-name>
          > > > verbose
          > > > </param-name>
          > > > <param-value>
          > > > true
          > > > </param-value>
          > > > </jsp-param>
          > > > </jsp-descriptor>
          > > >
          > > > </weblogic-web-app>
          > > > ---------------------
          > > >
          > > > so ... anything I did wrong, so the WLS can't do Session
          replication??!!
          > > >
          > > >
          > > > Please Help or Comment!
          > > >
          > > > Thanks in advance!
          > > >
          > > > with thanks,
          > > >
          > > > Alex Wong
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > >
          > >
          >
          >

Resetting targets WLS 6.1

Similar Messages

Maybe you are looking for