Jolt pool
we are running 3 internet applications in 1 weblogic server. we have correctly set 3 properties for the jolt pool since when we start the weblogic server, these jolt pools are initialized (weblogic console). we could also see that the session pool manager contains the session pools in the weblogic console (administrator). when we run the systems simultaneously, only 1 can connect to the jolt pool. we are wondering what causes the failure to connect to jolt. please help
I just found this message looking for the answer to the same question.
Does anybody have a clue about obtaining a Jolt session from a remote client in WL6+?
Thanks.
Similar Messages
-
Where is the jar file to have jolt.pool.*
hi,
where to find the jar files that have
bea.jolt.pool.DataSet;
bea.jolt.pool.Result;
bea.jolt.pool.SessionPool;
bea.jolt.pool.SessionPoolManager;
DoIf you are using Tuxedo 7.1 or 8 (or Tuxedo 6.x+Jolt), you should find
it in joltjse.jar under $TUXDIR/udataobj/jolt.
If you are using WLS 5.1, you should find in under
$WL_HOME/classes/bea/jolt/pool or in the service pack jar.
_shailesh
wei jiang wrote:
hi,
where to find the jar files that have
bea.jolt.pool.DataSet;
bea.jolt.pool.Result;
bea.jolt.pool.SessionPool;
bea.jolt.pool.SessionPoolManager;
Do -
Bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
I am ctreating the transaction object and try to operate PoolManager.call()
with the transaction object as parameter. The call fails with the following
exception:
bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
at bea.jolt.pool.Connection.call(Connection.java, Compiled Code)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at
mcs.connectjolt.bandetails.BanDetailesDAO.getBanDetailes(BanDetailesDAO.java
:87)
at
mcs.connectjolt.bandetails.BanDetailsBean.getBanDetailes(BanDetailsBean.java
:68)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl.getBanDetailes(BanDetailsBea
nEOImpl.java:105)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl_WLSkel.invoke(BanDetailsBean
EOImpl_WLSkel.java:83)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java, Compiled Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:69)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
My configuration: WebLogic 5.1, Jolt 1.2, Tuxedo 6.4.I am ctreating the transaction object and try to operate PoolManager.call()
with the transaction object as parameter. The call fails with the following
exception:
bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
at bea.jolt.pool.Connection.call(Connection.java, Compiled Code)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at
mcs.connectjolt.bandetails.BanDetailesDAO.getBanDetailes(BanDetailesDAO.java
:87)
at
mcs.connectjolt.bandetails.BanDetailsBean.getBanDetailes(BanDetailsBean.java
:68)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl.getBanDetailes(BanDetailsBea
nEOImpl.java:105)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl_WLSkel.invoke(BanDetailsBean
EOImpl_WLSkel.java:83)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java, Compiled Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:69)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
My configuration: WebLogic 5.1, Jolt 1.2, Tuxedo 6.4. -
Configure a BEA Jolt connection pool
The Jolt for Weblogic property in the property file is as follow :
eblogic.system.startupClass.demojoltpoolStart=\
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
weblogic.system.startupArgs.demojoltpoolStart=\
poolname=demojoltpool,\
appaddrlist=//10.0.0.7:8001,\
failoverlist=//10.0.0.7:8005,\
minpoolsize=1,\
maxpoolsize=3
weblogic.system.shutdownClass.demojoltpoolStop=\
bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
weblogic.system.shutdownArgs.demojoltpoolStop=\
poolname=demojoltpool
I couldn't get it connected, a message said 'Unable to connect to primary server at //10.0.0.7:8001'.
When is the reason?Hi there!
You have to start Tuxedo JOLT servers at the same address of parameters
"appaddrlist", and if you have security implemetation you have to add those
parameters.
You should use Jolt 1.2 in tuxedo Application
Best Regards
Mauricio
"Chaang" <[email protected]> wrote in message
news:[email protected]..
The Jolt for Weblogic property in the property file is as follow :
eblogic.system.startupClass.demojoltpoolStart=\
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
weblogic.system.startupArgs.demojoltpoolStart=\
poolname=demojoltpool,\
appaddrlist=//10.0.0.7:8001,\
failoverlist=//10.0.0.7:8005,\
minpoolsize=1,\
maxpoolsize=3
weblogic.system.shutdownClass.demojoltpoolStop=\
bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
weblogic.system.shutdownArgs.demojoltpoolStop=\
poolname=demojoltpool
I couldn't get it connected, a message said 'Unable to connect to primaryserver at file://10.0.0.7:8001'.
>
When is the reason? -
How to return jolt connection back to the joltpool?
hi
I used following codes to get joltconnection pool:
SessionPool sessionPool = sessionPoolManager.getSessionPool(poolName);
DataSet request = new DataSet(requestString.length()*2);
request.setValue("STRING", requestString);
Result result = sessionPool.call(serviceName, request, null);
return (String) result.getValue("STRING", null);
my question is : how to return jolt connection back to the joltpool? do I need
to do that?
when I used jdbc connection pool, I used conn.close() to return
to jdbc connection pool. Is there any method like "close()" in
jdbc connection?
Wei JiangHi,
The below is the simple source code using Pool which it is extracted from
BEA's support web site.
and it is helpful.
The Pool doesn't need to return jolt connection back to the joltpool.
because it is done by Pool Manager automatically.
import bea.jolt.*;
import bea.jolt.pool.*;
public class Pho2 {
public static void main(String argv[])
try
String[] adresses = new String[1];
adresses[0] = "//aglaia:7040";
// creation du manager et du pool par defaut
SessionPoolManager sessionPoolManager = new SessionPoolManager();
int i = sessionPoolManager.createSessionPool(adresses, null, 1, 3, new
UserInfo(), null);
SessionPool sessionPool = sessionPoolManager.getSessionPool(null);
DataSet dataset = new DataSet();
Result result=null;
dataset.setValue("rhaine","coucou");
try
result = sessionPool.call("TOUPPER", dataset, null);
catch(Exception Ex)
System.out.println("session");
Ex.printStackTrace();
System.out.println("dataset="+dataset);
System.out.println("result ="+result);
System.out.println("ApplicationCode="+(new
Integer(result.getApplicationCode())).toString());
catch(Exception Ex)
System.out.println(Ex.getMessage());
Hope this helps.
Mr, Ko.
"wei jiang" <[email protected]> wrote in message
news:[email protected]..
>
hi
I used following codes to get joltconnection pool:
SessionPool sessionPool = sessionPoolManager.getSessionPool(poolName);
DataSet request = new DataSet(requestString.length()*2);
request.setValue("STRING", requestString);
Result result = sessionPool.call(serviceName, request, null);
return (String) result.getValue("STRING", null);
my question is : how to return jolt connection back to the joltpool? do Ineed
to do that?
when I used jdbc connection pool, I used conn.close() to return
to jdbc connection pool. Is there any method like "close()" in
jdbc connection?
Wei Jiang -
Jolt 1.2/Tuxedo 6.5
I'm working on Tuxedo 6.5/Jolt 1.2 in a Websphere 3.02 environment.
1. Problem with Transaction and Session pools
Our application retreives information from an Informix database through servlets. We've built a SessionPool in order to access our Tuxedo services, but without any transactional state. In fact, as we do not update the database, we didn't use transactions.
Our question is when is the user connection free and available for an other user, since the Reference Documentation API says a connection is free when the transaction commit's or rollbacks. As we don't use any transaction, we don't know when (and how) a connection is available for reuse. Must we wait the Tuxedo timeout? ....
And is there an easy way to free a connection (force a connection to be once again available)?
2. Jolt 1.2 release
We're working with the Jolt 1.2 release, as I already said. The reference API documentation says a class named ServiceInfo in bea.jolt.pool will retreive information on Tuxedo services (parameters, ...). Unfortunately, our jar file (joltjse.jar, 33Kb) doesn't have it. I'd like to use it to built my DataSets' automatically from an Array or a Vector.
Is it because our Jolt version is too old and because the 1.2 does not provide this class? Is it part of the 1.2.x release?
In this case, how can I get the right jar without having to install (and/or upgrade to) a new version of Jolt?
Thank you for your answers
TR.Dear,
Could you please send Jolt 1.2<For AIX4.3> to me ?
Or tell me where I can find it.
Thanks anywhere.
Fogg wg -
Problems in jolt 1.2 with weblogic 6.1
Hi,
I am trying configure a jolt pool connection on startup of weblogic server.
I am using weblogic 6.1, tuxedo 6.5 server y jolt 1.2.
JSL is started.
I have copy $WL_HOME/classes/bea/jolt/pool from weblogic 5.1 to weblogic 6.1
I have defined a jolt pool, a startup class and a shutdown class.
I have not any problem on weblogic startup:
<Jan 13, 2003 5:21:06 PM CET> <Info> <WebLogicServer> <Invoking startup class:
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.startup(poolname=simpapp,appaddrlist=//69.51.23.140:13398,failoverlist=//69.51.23.140:13414,minpoolsize=1,maxpoolsize=15)>
<Jan 13, 2003 5:21:07 PM CET> <Info> <WebLogicServer> <bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
reports: Jolt Session Pool: simpapp initialized>
The problem is when a servlet try:
private SessionPoolManager b_mgr;
Environment env = new Environment();
Context ctx = env.getInitialContext();
b_mgr = (SessionPoolManager) ctx.lookup(SessionPoolManager.POOLMANAGER_NAME);
SessionPool session = (SessionPool) b_mgr.getSessionPool("simpapp");
The object session is always null.
Thx in advanceShashi,
Tuxedo 6.5 needs a patch to run on later versions of Solaris or else the WSNAT_CAT:1008 or JOLT_CAT:1008 "Error: Could not establish listening address on network +netaddr+" message can occur.
The thread Could not establish listening address on network describes a similar problem with the WSL, and the ULOG in that thread also indicates "TUXEDO Version 6.5 SunOS 5.5.1".
Please obtain the latest rolling patch from Oracle support. (It would be even better to upgrade to a later release of Tuxedo, since Tuxedo 6.5 is past its end of life date on Solaris. Hopefully whatever compilation problems you are having with later Tuxedo releases can be resolved fairly easily.)
Regards,
Ed -
JOLT JSL Load Balancing ?
Hello
Question: If I have hundreds of JOLT clients accessing Tux services behind a
firewall, can/should I load balance across multiple JRLYs? Has anyone done
this with a Cisco, F5 or other load balancer? Or have you instead just
tinkered with the "appAddress" on the JOLT client.
Here's why I ask:
From the JOLT 1.2 documentation...
- Under normal conditions, only one JRLY can communicate with one JRAD.
- A JRAD can only point to one JSL.
So given the constraints above, it would look something like...
JRLYx ------||-------JRAD-------------JSL/JSH (Node X)
FireW
JRLYy ------||-------JRAD-------------JSL/JSH (Node Y)
If all JOLT requests to go one JRLY, they will pound the JSL/JSH on one
node. So load balancing would be preferred and I'd like to do something
smarter than defining half the clients with appAddress=JRLYx and the other
half with appAddress=JRLYy.
Thanks for taking the time to read this. I would imagine I'm not the first
to run into this.
-JonJolt, by definition, requires a Tuxedo setup. By specifying multiple
addresses in the appaddrlist, the Jolt connection pool will distribute
the connections across the addresses supplied. So yes, the appaddrlist
is only used to establish the physical connection. The JoltPoolManager
will hand out the connections in such a way as to distribute the load
across the existing connections.
Hope this helps,
Robert
Laurent Nel wrote:
> Robert Patrick <[email protected]> wrote:
> >The Jolt connection pool can be configured to distribute
> >its connections
> >across multiple JSL on multiple machines (by specifying
> >more than one
> >address in the appaddrlist argument in the configuration
> >of the pool).
> >Obviously, once a request is sent from WLS to a specific
> >JSH process,
> >Tuxedo load-balancing is used to determine which Tuxedo
> >server will
> >process the request.
>
> So, does this requires a Tuxedo setup ?
> I would like to know if it is possible to do load-balancing using
> only the appaddrlist of the Jolt pool ?
> My understanding of this list is that it is used only to determine
> to which tuxedo server the jolt client is going to open a connection.
> The online doc says that the server is choosen 'randomly' (I guess
> that it means in a unpredictable way).
>
> Laurent
-
Jolt connections and WL 6.0
Hi-
I've been encountering some difficulty in migrating our application from
Weblogic 4.5.2 to 6.0. The issue right now is not being able to connect to
the Jolt pools that I've defined via the console. Whenever I try and connect
I receive the following error messages:
Unable to connect to primary server at 206.88.43.52:64560
Unable to connect to fail-over server at 206.88.43.52:64560
I've installed the Jolt client for WL6.0 and changed the code to connect
using the new method. I created the SimpAppServlet that is supplied in the
readme file for the Jolt client for Weblogic and receive the following
diagnostics when I run it.
This is the response from the SimpAppServlet:
Your request cannot be completed at this moment.
Diagnostic Message is: No sessions are available
Possible reasons:
No sessions are available
The session pool is suspended
The session pool is shutdown
Please resubmit your request later.
I found another message refering to this same issue in the newsgroup but the
only answer was to contact support (which I've done). Can anyone point out
where I've made my mistake?
TIA
-BrettFor future reference.... Jolt connection pools must be specified with
leading //'s before the ip address. It's always the simple things that bite
ya. -
Calling Tuxedo Service using BEA Jolt.
I'm trying to call Tuxedo service from java stored procedure using BEA JOLT.My normal java client works fine but when i use the same client as java stored procedure i get following error message :
can not connect to any //lucy:9021(host:port)
Reason:Nwhdlr:can not open socket
I've successfully loaded all required JOLT jar files using loadjava and created the procedure successfully .Java code is given below :
import bea.jolt.*;
import java.sql.*;
public class JoltToTux
public static void callTuxService() throws Exception
JoltSession session;
JoltSessionAttributes sattr;
JoltRemoteService toupper;
JoltTransaction trans;
String userName=null;
String userPassword=null;
String appPassword=null;
String userRole=null;
String outstr;
try {
sattr = new JoltSessionAttributes();
sattr.setString(sattr.APPADDRESS, "//lucy:9021");
sattr.setInt(sattr.IDLETIMEOUT, 300);
session = new JoltSession(sattr, userName, userRole,userPassword, appPassword);
toupper = new JoltRemoteService ("CB_EXESUB", session);
toupper.setString("CLFY_SUB", "PingSrvr");
toupper.call(null);
System.out.println( "Call to Tuxedo complete" );
outstr = toupper.getStringDef("WF_MESSAGE","" );
System.out.println("return string : " + outstr);
session.endSession();
System.exit(0);
} //end of try
catch (Exception e) {
// System.err.println(e.getMessage());}
e.printStackTrace();
} // end main
public static void main( String args[] ) {
try {
JoltToTux jt = new JoltToTux();
jt.callTuxService();
catch ( Exception e0 ) {
e0.printStackTrace();
} // end ToUpper
thanks
anuragAms,
You can't do that with JOLT. You will need to use the WTC product,
currently in beta - see WTC Questions and Answers
Regards,
Peter.
Got a Question? Ask BEA at http://askbea.bea.com
The views expressed in this posting are solely those of the author, and
BEA
Systems, Inc. does not endorse any of these views.
BEA Systems, Inc. is not responsible for the accuracy or completeness of
the
information provided
and assumes no duty to correct, expand upon, delete or update any of the
information contained in this posting.
Ams wrote:
Hi Manoj,
I want to call a tuxedo service and also want to update
database (using entity beabs) in same transaction so I
can't use AUTOTRAN , Am I right ?
I am using bea.jolt.pool.SessionPool's startTransaction
method to start a transaction and passing this
to SessionPool's call method.
Ams.
"Manoj SASIDHARAN" <[email protected]> wrote:
Hello Ams,
Could u plz give more information abt the usage scenario. Another way
to test
would be to put AUTOTRAN=Y for the service in question.
HTH
regards
MS
"Ams" <[email protected]> wrote:
Hi,
I am calling Tuxedo service from ejb using jolt.
I want the service call in transaction started in ejb.
I am getting following error.
LIBTUX_CAT:481: ERROR: Service xa_start returned -7
Does jolt support transaction ?
Ams
[att1.html] -
NoClassDefError with jolt and WLS 6.1
I'm trying to access a servlet I made(based on the SimpAppServlet that comes with
jolt)
I successfully installed it successfully on Tomcat3.2.2 and WLS5.1 but am having
difficulty with WLS6.1-beta.
I can compile with no errors but when I try to access it i get the following error:
java.lang.NoClassDefFoundError: bea/jolt/pool/ApplicationException
joltjse.jar is in the classpath so that's not the problem.
If anybody has any ideas that would be greatly appreciated.solved
The startweblogic.cmd script was resetting the classpath
had to edit before it could recognize the jar file.
Clem
"Clem" <[email protected]> wrote:
>
I'm trying to access a servlet I made(based on the SimpAppServlet that
comes with
jolt)
I successfully installed it successfully on Tomcat3.2.2 and WLS5.1 but
am having
difficulty with WLS6.1-beta.
I can compile with no errors but when I try to access it i get the following
error:
java.lang.NoClassDefFoundError: bea/jolt/pool/ApplicationException
joltjse.jar is in the classpath so that's not the problem.
If anybody has any ideas that would be greatly appreciated. -
Jolt/WLS5.1- ServiceException on JoltRemoteService call
We are making a call to a tuxedo 6.5 service (TAD_D_GENGW) via a Jolt 1.2 pool
in weblogic 5.1 service pack 8 and occasionally receive an error (see below).
How can I get additional detail on this type of exception? Specificially, given
that it's a ServiceException, is there a WLS config change that I can make to
get WLS to log the Tuxedo error associated with this message? I'm guessing it's
a timeout, but don't know how to verify this guess short of modifying the developer's
code which makes the call.
Any assistance is greatly appreciated.
Thanks,
Bruce
bea.jolt.pool.ServiceException: bea.jolt.JoltRemoteService(TAD_D_GENGW)c
all()
bea.jolt.pool.ServiceException: bea.jolt.JoltRemoteService(TAD_D_GENGW)call()
at bea.jolt.pool.Connection.call(Connection.java:277)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at com.uprr.jmsgapi.JoltMsgRequest.Request(JoltMsgRequest.java:659)
at com.uprr.shared.jmsgapi.jmsgapiRouterImpl.send(jmsgapiRouterImpl.java
:121)
at com.uprr.shared.jmsgapi.jmsgapiRouterImpl.send(jmsgapiRouterImpl.java
:79)
at ...We are making a call to a tuxedo 6.5 service (TAD_D_GENGW) via a Jolt 1.2 pool
in weblogic 5.1 service pack 8 and occasionally receive an error (see below).
How can I get additional detail on this type of exception? Specificially, given
that it's a ServiceException, is there a WLS config change that I can make to
get WLS to log the Tuxedo error associated with this message? I'm guessing it's
a timeout, but don't know how to verify this guess short of modifying the developer's
code which makes the call.
Any assistance is greatly appreciated.
Thanks,
Bruce
bea.jolt.pool.ServiceException: bea.jolt.JoltRemoteService(TAD_D_GENGW)c
all()
bea.jolt.pool.ServiceException: bea.jolt.JoltRemoteService(TAD_D_GENGW)call()
at bea.jolt.pool.Connection.call(Connection.java:277)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at com.uprr.jmsgapi.JoltMsgRequest.Request(JoltMsgRequest.java:659)
at com.uprr.shared.jmsgapi.jmsgapiRouterImpl.send(jmsgapiRouterImpl.java
:121)
at com.uprr.shared.jmsgapi.jmsgapiRouterImpl.send(jmsgapiRouterImpl.java
:79)
at ... -
Simple Servlet Example - Using Tuxedo JOLT
Hi
I am trying to run the sample Tuxedo provided application which uses Servlets. I had configured JSL & JSH properly and had booted the Tuxedo Service and they are all running properly.
I have WebLogic Server installed and had created the JoltSessionPool with name "samplejoltpool" and had also defined the StartupClass & ShutdonClass. While defining the JoltSessionPool i had given min services as 5 and max services as 10 becasue I used the following definition for JSL in UBBCONFIG.
CLOPT="-A -- -n //172.20.34.17:7777 -m5 -M10 -x5"
No as per the guide they are asking me to Restart WebLogic Server when I did so. I got an error I went into WebLogic Log and found out the following in the Log. It states
CRITICAL [06:52:35] (JDKLog4jAdapter.java:log:80) - Failed to invoke startup class "TuxedoStartupClass", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=demojoltpool,Type=JoltConnectionPool : Cannot create 5 connections
The Entire Trace from the Log file is:
NOTICE [06:52:34] (JDKLog4jAdapter.java:log:80) - The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.
INFO [06:52:34] (JDKLog4jAdapter.java:log:80) - Initialized the Diagnostic Accessor Service.
INFO [06:52:34] (JDKLog4jAdapter.java:log:80) - Invoking bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(null)
CRITICAL [06:52:35] (JDKLog4jAdapter.java:log:80) - Failed to invoke startup class "TuxedoStartupClass", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=demojoltpool,Type=JoltConnectionPool : Cannot create 5 connections
java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=demojoltpool,Type=JoltConnectionPool : Cannot create 5 connections
at bea.jolt.pool.servlet.weblogic.impl.PoolManagerStartUpJMX.startup(PoolManagerStartUpJMX.java:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(PoolManagerStartUp.java:38)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppActivation(ClassDeploymentManager.java:158)
at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Can someone help me out to overcome this error. The JooltSessionPool entry properties are as below.
Name : demojoltpool
Min Pool Size : 5
Max Pool Size : 10
Recv Timeout : 30
Prim Addr : //172.20.34.17:7777
With Regards
Venkat
Tata Consultancy Services
IndiaThe problem was with JVM total memroy available when I try to create 5 Session Pools the JVM memeory goes to 97% that is the main reason why it is failling. I restarted all the processes in the server now it seems to be working fine without any issues.
-
OutOfMemoryException with jolt invoking.
hi~!
I installed WLS6.1sp1 with Tusxedo and jolt.
Then i started the WLS server, and i met "OutOfMemoryException when invoking jolt".
It was fine when i configured "2" Maximum pool size and "2" Minimum pool size.
But the minimum & maximum pool sizeHi~~
The heap setting was mx1024m. And the MaxPermSize was 131072k.
I think the reason of the "OutOfMemoryException" is related with the kernel parameter.
(the machine is HPUX 11i - superdome.)
But I have no idea how do i set the kerenl paremeters and about the exact relation
between memory and kernel parameters
And when i set the kernel parameters, is there any basis or canons or standards?
Plz give me some ideas....
thansk for your concern...
peace~!
Eugene.
Michael Young <[email protected]> wrote:
Hi.
What are your heap settings? What happens when you increase the heap?
Thanks,
Michael
Eugene NOH wrote:
sorry...the message was incomplete..
When the maximum & minimum jolt pool size were more than "2", the "OutOfMemoryException"ocurred.
How can i handle this situation..?
please help~~!!
regard...
eugene.--
Michael Young
Developer Relations Engineer
BEA Support -
JoltConnectionPool can not start in weblogic server
Hi
I am trying to run the sample Tuxedo provided application which uses Servlets or Ejb.
Now the Tuxedo Server has been configured and running properly.
I have WebLogic Server installed and had created the JoltSessionPool with name "MAJoltConnectionPool" and had also defined the StartupClass & ShutdonClass.
While defining the JoltSessionPool i had given min services as 1 and max services as 5 and others as default,
and the JoltSessionPool's target is a weblogic managed server which named ct2.
Then i tryed to start the ct2 server on command line such as:
startManagedWebLogic.cmd ct2 http://localhost:7001
I got an error in starting "MAJoltConnectionPool" but the server ct2 is starting normally.
Anyone who can help me to find out the reason? Thanks a lot.
The Command Line window shown following in the Log:
Failed to invoke startup class "MAJoltPoolStart", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool :
Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
The Entire Trace from the Log file is:
####<Mar 16, 2011 11:58:35 AM CST> <Notice> <Log Management> <HXU49> <ct2> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915024> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<Mar 16, 2011 11:58:35 AM CST> <Info> <Diagnostics> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915070> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
####<Mar 16, 2011 11:58:35 AM CST> <Info> <WebLogicServer> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915078> <BEA-000256> <Invoking bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(null)>
####<Mar 16, 2011 11:58:35 AM CST> <Critical> <WebLogicServer> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915239> <BEA-000286> <Failed to invoke startup class "MAJoltPoolStart", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool : Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool : Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
at bea.jolt.pool.servlet.weblogic.impl.PoolManagerStartUpJMX.startup(PoolManagerStartUpJMX.java:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(PoolManagerStartUp.java:38)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
>
####<Mar 16, 2011 11:58:35 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247915288> <BEA-000365> <Server state changed to ADMIN>
####<Mar 16, 2011 11:58:35 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247915313> <BEA-000365> <Server state changed to RESUMING>
####<Mar 16, 2011 11:58:36 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247916769> <BEA-000365> <Server state changed to RUNNING>
####<Mar 16, 2011 11:58:36 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247916770> <BEA-000360> <Server started in RUNNING mode>
With Regards
HanHi
To resolve this problem , you have 2 solutions:
- modify the config.xml file to add in the tag <security-configuration> the following line :
<clear-text-credential-access-enabled>true</clear-text-credential-access-enabled>
or
- check the checkbox "Clear Text Credential Access Enabled" in the settings for the domain / security / general / advanced
restart the weblogic server to activate this change if necessary (Normaly, no restarts are necessary with weblogic server v10.3.5.0)
Hope this reponse help you (if it's not too late ;-) )
Laurent.
Maybe you are looking for
-
Grant permission through dynamic parameters entered by user through web app
This is my code. f1=request.getParameter("URL"); out.println("parameter f1 ===>"+f1);//user name f2=request.getParameter("URL1"); out.println("parameter f2 ===>"+f2);//table name f3=request.getParameter("URL2"); out.println("parameter f3 ===>"+f3);//
-
I have problem with receive mail. IOException "no content". My code: Folder folder = store.getFolder("INBOX"); folder.open(javax.mail.Folder.READ_ONLY); Message[] message = folder.getMessages(); for (int i =0; i< message.length; i++) { Part messagePa
-
I've accessed the User Interface dialogue in Xfce's System Settings to change the font appearance in Xfce4-beta and indeed everything is altered correctly -- except for the title bar which continues to use the Sans font. What should I do to get that
-
Using two different versions of iMovie...Please help!!
I am new to using iMovie and need to know whether it is possible to jump between two different versions of iMovie on two different computers. I have created my movie on a computer using a higher version and need to put it onto a computer using a lowe
-
I'm a little confused. I know that using private instance variables is good practice, and that the appropriate way to access those variables is with accesser methods (getXXX(), etc.). Since the variables are private, you can't access them by just ref