Transaction difference in WLS 5.1 & WLS 6.1

I have a CMP that does a simple read & update on a file on the AS400. When I
run
this on version 5.1 of Weblogic everything works fine. When I run the same exact
bean
on version 6.1 of WLS I get an SQLException that looks like this.
=======
java.sql.SQLException: [SQL7008] IN901F in DATAIP not valid for operation.
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:359)
at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatem
ent.java:570)
at com.ibm.as400.access.AS400JDBCPreparedStatement.executeUpdate(AS400JD
BCPreparedStatement.java:914)
at weblogic.jdbc.jts.Statement.executeUpdate(Statement.java:503)
at com.as400.product.ejb.In901f_yrautr__WebLogic_CMP_RDBMS.ejbStore(In90
1f_yrautr__WebLogic_CMP_RDBMS.java:1207)
====
I found a couple of newsgroups that suggest this type of error is due to "journaling"
not being turned on for that file. Journaling deals with commit / rollback functionality
on the AS400. That would suggest to me that it has to do with my transaction
settings
in my bean, but I have all transactions set to "Never". So my question is, why
would
this work on WLS 5.1 but not on WLS 6.1?? Both versions are using the exact same
file with journaling turned off. It is an EJB 1.1 bean. Any ideas other than
trying to turn on the journaling feature for that file??

Similar Messages

Message transmission from Wls 7 to Wls 8 and then to Wls10

Hi All,
We are currently doing a POC in which we are using Wls 7, Wls 8.1 and Wls 10 . The basic idea of the POC is that we need to post a message on Wls 7, and from Wls 7 the message should reach Wls 8.1 and inturn from Wls 8.1 it should reach Wls 10. For this communication to take place we have configured message bridges on the respective servers.
But the problem that we are facing is, we are not bale to transmit message from one Wls server to other, from Wls 7 to Wls 8 and also from 8 to 10.
We are gettin the following error:-
<Error> <Security> <090473> <ServerIdentity failed validation, downgrading to anonymous.>
Can anybody please help on this.
Regards,
Rakesh

If this is just a POC, you might try enabling Domain Trust on each of the domains (here is the 10.3 link, probably different in 8.1 and 7.0):
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/security/EnableTrustBetweenDomains.html
In a production environment there are other security implications for doing this willy nilly, that I recommend you read the docs and post questions in the WLS Security forum.

Functional transactional difference between SAP version 4.7 and ECC 6.0

Hi Experts,
Can you Pls tell the Functional transactional difference between SAP version 4.7 and ECC 6.0 in case of Sales and Distribution module.
Like VA05n is one transactional difference,Pls tell the others?
Regards,
Rohan

Hi,
there are lot of changes like i observe
1, in rebates there is no advanced rebate processing in 4.7
2. there is no scale group field in condrecords of agrement in rebate agreement.
3. there are lot of new reports available in SIS
4. in sales returns process also seperate config available in 6.0
regards,
sk

Functional Transactional difference in SAP 4.7 and ECC 6.0 in SD

Hi Experts,
Can you Pls tell the Functional transactional difference between SAP version 4.7 and ECC 6.0 in case of Sales and Distribution module.
Like VA05n is one transactional difference,Pls tell the others?
Regards,
Rohan

Hi,
When i started working on upgrade projects, gathered some infor, here iam sharing that,
ECC 6.0 New GL Functionality
1.Activate the New General Ledger Accounting by a single
click on the clock icon
2.You will reach to change view "activation of New GL A/cg"
detail screen and tick the checkbox and save.
3. After activation of New General Ledger Accounting, you
exit the IMG screen when you re-enter, you find that a new
node is added Financial Accounting (New)
4.After activation of New General Ledger Accounting; a new
sub node appears in the IMG structure.
This sub node is Define Segment
The menu path is:
SAP Customizing IMG ---> Enterprise Structure -
>
Definition --> Financial Accounting --> Define Segment
In this IMG activity, you define your segments.
If you then define your profit centers, you can enter an
associated segment in the master record of a profit center.
The segment is then derived from the assigned profit center
during posting.
5. Activation has created a new field in Profit Center
Master Record: the SEGMENT
6.Leading and Non- Leading Ledgers
In General Ledger Accounting, you can use several Ledgers
in parallel. This allows you to produce financial
statements according to different accounting principles. A
ledger uses several dimensions from the totals table it is
based upon. When defining Ledgers, one must be defined as
the Leading Ledger. The Leading Ledger is based on the same
accounting principles as that of the consolidated financial
statements. It is integrated with all subsidiary ledgers
and is updated in all company codes. This means that it is
automatically assigned to all company codes. In each
company code, the Leading Ledger receives exactly the same
settings that apply to that company code : the currencies,
the fiscal year variant and posting period variant .
You must designate one of your ledgers as the Leading
Ledger. It is not possible to designate more than one
ledger as the leading ledger.
The menu path is:
SAP Customizing IMG -
> Financial Accounting (New) -
>
Financial Accounting Basic Settings (New) -
> Ledgers ---
-> Ledger -
> Define Ledgers for General Ledger
Accounting
Clicking on the checkbox identifies one of your ledgers as
the Leading Ledger.
7. Activation of Non Leading Ledgers
Non Leading Ledgers are parallel ledgers to the Leading
Ledger . They can be based on local accounting principle,
for example. You have to activate a non- Leading Ledger for
individual company codes. Non- Leading Ledgers can have
different fiscal year variants and posting period variants
per company code to the Leading Ledger of this company
code.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
---> Ledger -
> Define and Activate Non --Leading
Ledgers
8.Assign scenarios to ledgers
A Scenario combines Customizing settings from different
business views. Each business view specifies which posting
data is transferred from different application components
in General Ledger Accounting, such as cost Center update or
Profit Center update .You assign the desired scenarios to
your ledgers. For each ledger, you define which fields are
filled with posting data from other application components.
SAP delivers a number of scenarios in the standard system.
It is not possible to create additional scenarios.
The menu path is:
SAP Customizing IMG -
> Financial Accounting (New) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
--->Fields -
> Display Scenarios for General Ledger
Accounting.
9. Cost of sales accounting
Cost of sales accounting is a way to create a profit and
loss statement (P&L) for a company by comparing the
revenues to the costs or expenses incurred to obtain these
revenues.
The expenses are mainly divided by functional area such as:
Manufacturing
Administration
Sales
Research and Development
We can activate Cost of Sales Accounting by the following
menu path :
SAP Customizing IMG -
> Financial Accounting ( New ) -
-> Financial Accounting Basic Settings (New) -
>
Ledgers ->Ledger---> Activate Cost of Sales Accounting
Offsetting Account Report ECC 5.0
Offsetting account report for vendors in ECC 5.0 is
possible after implementing the OSS Note 1034354
Regards
Arani Bhaskar

Functional Transaction Difference between SAP 4.7 and ECC 6.0 in Case of SD

Hi,
Experts can you Pls tell Transaction difference between SAP 4.7 and ECC 6.0 in case of SD module.
Like VA05n is one transactional difference.
regards,
Rohan

Refer below for the Transaction codes, You can find the functional differences in Release note or Solution browser > Apart from the functional Delta most of the reports are in ALV Grid disply and few changes you can note in Organizational Structure Assignment and consistency check , Document flow , Purchase Order Data tab and Item Conditions so on
VA05N List of Sales Orders
VA25N Quotation List
VF05N Billing Document List
VA45N List of Contracts
OVX8N Check Report Organization Sales
OVX3N Assign sales organization to company code
OVXKN Assign distribution channel to sales organization
OVXAN Assign division to sales organization
OVXGN Set up sales area
OVXMN Assign sales office to sales area
OVXJN Assign sales group to sales office
OVX6N Assign sales organization - distribution channel - plant

XA transactions with JMS connector (with BEA WLS)

Hello,
are XA transactions supported by JMS connector when communicating with BEA WLS (version 8.1)?
Thanks
Tomas

Hi
Yes
Check this JMS FAQ
http://www.google.com/url?sa=t&ct=res&cd=1&url=https%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fgo%2Fportal%2Fprtroot%2Fdocs%2Flibrary%2Fuuid%2F604e2b64-e689-2910-64b3-ffd650f83756&ei=LcmERubLL4fgsALL6snWDw&usg=AFQjCNHbiooj-7G5g6w4tVVZQiRuQ5XQ_A&sig2=tpxbhUpIKR5oSe3aab8h4w
regards
krishna

Corba - differences between WLS 7.02 / WLS 8.1

In WLS 7.02 the following piece of code works, but in WLS 8.1 I get an exception
on the last line (see the log below). Would someone have a clue why it’s not working
with WLS 8.1
Note: if you want to send me an email, remove the NOSPAM
TIA !
public OimSessionInstance openSession() throws EomSessionException {
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");
EomSessionException: class EomSession, method corbaConnection to OIM : exception
: org.omg.CORBA.MARSHAL: Exception waiting for response; nested exception is:
java.io.EOFException: GIOP protocol error vmcid: 0x0 minor code: 0
completed: No
at EomDefaultConnection.openSession(EomDefaultConnection.java:114)
at EomSession.<init>(EomSession.java:78)

"Alain Pigeon" <[email protected]> wrote:
>
In WLS 7.02 the following piece of code works, but in WLS 8.1 I get an
exception
on the last line (see the log below). Would someone have a clue why it’s
not working
with WLS 8.1
Note: if you want to send me an email, remove the NOSPAM
TIA !
public OimSessionInstance openSession() throws EomSessionException {
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");
EomSessionException: class EomSession, method corbaConnection to OIM
: exception
: org.omg.CORBA.MARSHAL: Exception waiting for response; nested exception
is:
java.io.EOFException: GIOP protocol error vmcid: 0x0 minor
code: 0
completed: No
at EomDefaultConnection.openSession(EomDefaultConnection.java:114)
at EomSession.<init>(EomSession.java:78)Found a solution:
In WLS7.0 the code automatically returned the SUN ORB found in the rt.jar. But
in WLS8.1 you have to force it to the SUN ORB by specifying it in the properties
file used to instantiate the ORB.
Example:
public OimSessionInstance openSession() throws EomSessionException {
String ORBClassName = "com.sun.corba.se.internal.iiop.ORB";
String ORBSingletonClassName = "com.sun.corba.se.internal.corba.ORBSingleton";
Properties props = new Properties();
props.put("org.omg.CORBA.ORBClass" , ORBClassName);
props.put("org.omg.CORBA.ORBSingletonClass" , ORBSingletonClassName);
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");

JSTL WLS 7 to WLS 8.1 Upgrade Issues

We have a web app that currently runs on WLS 7. We have been asked to upgrade the app to WLS 8.1 recently. Most of the screen have ported fine, but there are a couple of screens that seem to be throwing fits. It could be a JDK/JRE issue, but here is the scenario
          jstl looks up a string variable property which is set to either "Y" or "N". Using WLS 7, it comes back as either "Y" or "N". But when I run the same code with WLS81, it comes back as "true" or "false".
          Looking at the property right before it returns always shows the correct value. When I look into the parameters and values, they seem to match the above statements as well (Y,N,true,false).
          Here is an interesting twist though. If I switch the JDK to 1.4 on WLS7, it also changes to "true" and "false". I have tried both sun and jrockit jvms to no avail.
          Has anyone seen this behavior?
          Thanks,
          Ashar

That's almost what I said but not quite, you should not have any trouble, but this is the real world hence my suggestion to backup properly first.
As for Yosemite I don't know the answer yet, I would expect it to be a no but we'll have to wait and see.

EJB Migration Problem (WLS 9.2 = WLS 10.3.2)

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

Webservice Migration Problems (WLS 9.2 - WLS 10.3.2)

Hi,
we're upgrading our weblogic server from version 9.2 to 10.3.2. Everything runs just fine in my testing environment except for the webservices we have.
We have 6 webservices (JAX-RPC) which use a generic set of xml schema types to which each webservice offers specialized types that extend the supertype. Here comes the problem: The ant tasks wsdlc and clientgen from wls 9.2 generates java classes that do extend from the superclass. Unfortunatley the same call from the wls 10.3.2 results in a loss of class hierarchy.
Example:
<xs:complexType name="personinfo">
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="fullpersoninfo">
<xs:complexContent>
<xs:extension base="personinfo">
<xs:sequence>
<xs:element name="address" type="xs:string"/>
<xs:element name="city" type="xs:string"/>
<xs:element name="country" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
On WLS 9.2 this results in the following:
class Personinfo {
class Fullpersoninfo extends Personinfo {
On WLS 10.3.2. the result differs:
class Personinfo implements Serializable {
class Fullpersoninfo implements Serializable {
Is there any way to tell the wls 10.3.2 to generate a jax-rpc webservice that obeys the extension directive?
I look forward to your replies =)
Regards,
Johannes Bialek

Hi Jay,
thanks for the reply. Unfortunately using the other ant task doesn't seem to help. This is a WLS8.2 Version of Clientgen (which used the attribute "clientjar" rather than "destDir"/"destFile" and expected "packagename" as a required parameter). I tried id and it seems to have a couple of problems with schema files imported in included schema files. I worked around this by importing in the schema files from the wsdl itself, but now I get a "weblogic.xml.schema.binding.BindingException: ERROR: during code compilation".
Full stack trace:
weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
at weblogic.xml.schema.binding.internal.codegen.Compiler.invoke_compiler(Compiler.java:581)
at weblogic.xml.schema.binding.internal.codegen.Compiler.compile_descriptors(Compiler.java:380)
at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:290)
at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addTypesInSchemas(XSDTypeMappingBuilder.java:140)
at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSchemaTypes(TypeMappingBuilderBase.java:310)
at weblogic.webservice.tools.build.internal.Schema2JavaImpl.doTypeMapping(Schema2JavaImpl.java:317)
at weblogic.webservice.tools.build.internal.Schema2JavaImpl.run(Schema2JavaImpl.java:204)
at weblogic.webservice.tools.build.internal.WSDL2JavaImpl.run(WSDL2JavaImpl.java:258)
at weblogic.webservice.tools.build.internal.ClientGenImpl.getTypeMappingFromWSDL(ClientGenImpl.java:747)
at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFromWsdl(ClientGenImpl.java:419)
at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenImpl.java:359)
at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doClientGen(ClientGenTask.java:375)
at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:229)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.io.IOException: Compiler failed executable.exec: null
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.xml.schema.binding.internal.codegen.Compiler.invoke_compiler(Compiler.java:575)
... 41 more
Shouldn't we be able to use a 9.2 weblogic.jar for creating webservices that run on a 10.3.2?
Regards,
Johannes

WLS 6.1 - wls 5.1 lookup.

Hi
I face a problem with having to lookup an EJB hosted on a 5.1 server from a
6.1 server.
As I've read in an earlier post in this newsgroup WLS6.1 -> 5.1 naming
factories are not compatible. (Resulting in a
javax.naming.CommunicationException)
As the classnames and packages are identical on 5.1 and 6.1 for JNDI
including the 5.1 factory in the server's classpath is not an option.
Does anyone know of a workaround? (Or a magical compatiblity switch or
something...)
Best regards.
Trond Strømme, Software Engineer, mogul technology.

I think you can recompile the 5.1 EJB with the -iiop option and access it with
env.put(Context.PROVIDER_URL, "iiop://somehost:7001");
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
I haven't tried this between 6.1 and 5.1 but it works between 6.1 and 6.0 which
are also incompatible for normal t3 communication.
See: http://e-docs.bea.com/wls/docs61/rmi_iiop/API_rmi_iiop.html#1054561
for mmore details.
trond strømme wrote:
Hi
I face a problem with having to lookup an EJB hosted on a 5.1 server from a
6.1 server.
As I've read in an earlier post in this newsgroup WLS6.1 -> 5.1 naming
factories are not compatible. (Resulting in a
javax.naming.CommunicationException)
As the classnames and packages are identical on 5.1 and 6.1 for JNDI
including the 5.1 factory in the server's classpath is not an option.
Does anyone know of a workaround? (Or a magical compatiblity switch or
something...)
Best regards.
Trond Strømme, Software Engineer, mogul technology.

WLS/IIS - protect WLS http service

Hello,
we are currently investigating the use of WLS with IISproxy. IIS is our
preferred web server as we have to use a plugin on top of the web server
that is only available for IIS. This plugin is a tool to protect the web
server.
Our goal is to protect the access to our site with this plugin. So I
have some questions around the protection of the WLS http service:
Can I disable the webLogic HTTP service? The logic says No as IIS has
to proxy te request to this service.
Can I restrict the access to the webLogic HTTP service based on the IP
address of the client? In other words, I just want IIS able to talk to
WLS http service.
franck
PS: We use WLS 5.1 sp6.

Check the spelling of the property name. According to
http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/security/net/Conn
ectionFilter.html it's connectionFilter not ConnectionFilter.
Also, be aware there are security holes in WL 5.1 prior to SP9, don't leave
it into production on SP6 only
"Franck Fourel" <[email protected]> wrote in message
news:[email protected]..
>
I have a look to this connection filter. This is what we need.
I've tried to install it on my server (wls 5.1 sp6), but it does not work.The
WLS log says that the connection filter property
(weblogic.security.net.ConnectionFilter) is not correct: "Found undeclared
property" in the log and the server does not restart when this property is
set.
Is there some limitations to use this filter with the WLS version we use ?
thanks
Alf wrote:
Check
"Installing a Connection Filter",
http://e-docs.bea.com/wls/docs60/adminguide/cnfgsec.html#1063398 and
"Filtering Network Connections" in
http://e-docs.bea.com/wls/docs60/security/prog.html
"Franck Fourel" <[email protected]> wrote in message
news:[email protected]..
Hello,
we are currently investigating the use of WLS with IISproxy. IIS is
our
preferred web server as we have to use a plugin on top of the webserver
that is only available for IIS. This plugin is a tool to protect theweb
server.
Our goal is to protect the access to our site with this plugin. So I
have some questions around the protection of the WLS http service:
Can I disable the webLogic HTTP service? The logic says No as IIS has
to proxy te request to this service.
Can I restrict the access to the webLogic HTTP service based on theIP
address of the client? In other words, I just want IIS able to talk to
WLS http service.
franck
PS: We use WLS 5.1 sp6.

Delta Transaction Differences between 4.6C and ECC 6.0

Hi Experts,
For a given SAP Standard transaction, is there any SAP Program / Function Module which can give the delta transaction analysis.
Thanks in advance.
Best Regards,
Raghunahth L

Hi
Please use this link
http://solutionbrowser.erp.sap.fmpmedia.com/
Hope this will help u,
Please reward points if its use full
Regards,
MS

Oracle 11g Support For WLS 10 and WLS 9.2

Hi,
Does anyone know where I can find out definatively when Weblogic 10 and 9.2 will officially support Oracle 11g ?
Any official BEA sources here.
Cheers
Simon

There is only one real answer here: test it and test it thoroughly. Asking this question here is pointless, you cannot trust anyone here to give you advice you can rely on. Whatever is said, you have to validate the claims anyway.
Or did you think that Oracle employees were going to answer your question? If so, you are sadly mistaken. Oracle charges money for giving technical support.

2 vs 1 instance of WLS ?

Greetings !!!
Leaving other parametes same, would 2 instances of WLS with smaller
values of Heap size, executeThreadCount, DBConnections etc. each would
provide better perfrormance than one instances of WLS with higher number
for these paramaters ? Has anyone done benchmarks for such a scenario???
Environement: 2-CPU box, 1GB RAM, Solaris 6, JDK_1.2.2_05a & WLS
5.1-SP5
Thanks for your help/suggestions/pointers???
Sam

Mike,
Originally, the 'more, smaller instances' was a work-around for poorgarbage
collection. I believe that the later JDK's are much better at it. Wouldn'tit
make more sense to simply fix the garbage collection?There is the GC issue, but it is mostly a non-issue now with Hotspot. IBM's
JDKs also have much-improved GC implementations.
It's a queuing theory thing - 1 pool of 50 db connections will be able tostand
more load than 2 pools of 50 db connections, or 10 pools of 5 dbconnections.
Same goes for execution threads.Au contraire ... the front queue (e.g. a hardware load balancer) may
subscribe to that theory, but consider the bank vs. the check-out line
example from CS 101.
However, I don't believe that is the real issue. It's all about how many
requests you complete per second per unit of hardware. Obviously if one
instance works the best, then you stick with that.
Oh, I forgot one - when you start up a cluster with many instances, yournetwork
traffic goes wild. I think this was fixed around 4.5.1 SP 10.Are you telling me that there was a release of WL before 5.1? ;-)
And they have 'director' in front of their names.See below.
Peace,
Director Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Mike Reiche" <[email protected]> wrote in message
news:[email protected]...
>
"Cameron Purdy" <[email protected]> wrote:
Hi Mike,
Someone needs to send this to www.urbanlegends.com.I'd like to do some testing with WL6.0/JDK1.3/Hotspot 2.0/Solaris 8 etc.,
and in that case you might be right. On some systems, you can crank the
execute threads way up and it won't make a difference -- the system will
not
get saturated.Originally, the 'more, smaller instances' was a work-around for poorgarbage
collection. I believe that the later JDK's are much better at it. Wouldn'tit
make more sense to simply fix the garbage collection?
Let's see what else - you also have to cut your connection pool sizes
in
half.
Most apps keep the pool size about the same as the exec thread count.It's a queuing theory thing - 1 pool of 50 db connections will be able tostand
more load than 2 pools of 50 db connections, or 10 pools of 5 dbconnections.
Same goes for execution threads.
Oh, I forgot one - when you start up a cluster with many instances, yournetwork
traffic goes wild. I think this was fixed around 4.5.1 SP 10.
We run two instances per box here and I wish we didn't.Based on your stated feelings, is there any reason why you run two
instances
per box?Because there are people here that read about what what a great
idea it was. And they have 'director' in front of their names.
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Mike Reiche" <[email protected]> wrote in message
news:[email protected]...
Someone needs to send this to www.urbanlegends.com.
Using two instances vs. one instance doubles all kinds of things -
memory
required, overhead,
context switching, all class loading and JSP compiling, configuration
and
maintenance. And if you
use the same jsp workingDir for both WLS the two WLS will overwrite
each
other's generated
class files. (and they don't warn you about that in the doc). Let's seewhat else - you also have
to cut your connection pool sizes in half.
If you're not getting enough concurrency, then increase the number ofexecuteThreads.
If you want reliability, then fix whatever is breaking. It always
better
to not fail than to
recover nicely from a failure.
We run two instances per box here and I wish we didn't.
Mike
"Cameron Purdy" <[email protected]> wrote:
Sam,
It is best to test with your particular application but ... in most
cases,
adding a second instance of WebLogic to a particular host will make
more
effective use of the processor(s) in the server. Since you are payingper
processor, why not take full advantage of them? ;-)
Also, using two network interfaces, you can bind one WL instance to
one
NIC
and the other WL instance to the other NIC and thus not lose the site
if
one
of the networks goes down. (I don't know yet how to force WL to
assign
the
secondary from the other network, though.)
The main variable that you are looking for is throughput: Can you
handle
more concurrent requests? This measurement is basically the number of
typical requests per period of time that are possible before you seethe
server queues growing. In other words, once the server queues start
growing, that means that your cluster isn't managing to keep up, andyou
have lost the war.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"sam ernie" <[email protected]> wrote in message
news:[email protected]...
Greetings !!!
Leaving other parametes same, would 2 instances of WLS with smaller
values of Heap size, executeThreadCount, DBConnections etc. each
would
provide better perfrormance than one instances of WLS with highernumber
for these paramaters ? Has anyone done benchmarks for such ascenario???
Environement: 2-CPU box, 1GB RAM, Solaris 6, JDK_1.2.2_05a & WLS
5.1-SP5
Thanks for your help/suggestions/pointers???
Sam

Transaction difference in WLS 5.1 & WLS 6.1

Similar Messages

Maybe you are looking for