Integrating WebSphere MQ 5.3 with BEA Weblogic Server 9.2 3M

I am trying to integrate WebSphere MQ 5.3 with BEA WebLogic Server 9.2 3M. I have found the guide:
Integrating WebSphere MQ 6 with BEA Weblogic Server 10 using Weblogic Server's Foreign (JMS) Server feature [http://ibswings.blogspot.com/]. I have done all steps according this guidance.
I have made modification since, WebLogic Server 9.2 3M does not support EJB 3.0, I am using EJB 2.1, any changes that have been made is create ejb-jar.xml file and configure it according next guide
At the final step when I am deploying service-jar-files (for ex. ejb.jar), I am able to complete this procedure.
When I am starting service (for ex. ejb.jar) from Deployments I am facing a wall: exception appears
weblogic.application.ModuleException: Exception starting module: EJBModule(EJB)
Unable to deploy EJB: EJB.jar from EJB.jar:
com/ibm/mq/jmqi/system/JmqiComponent
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:505)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:18
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.NoClassDefFoundError: com/ibm/mq/jmqi/system/JmqiComponent
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at com.ibm.msg.client.wmq.factories.WMQFactoryFactory.createProviderXAConnectionFactory(WMQFactoryFactory.java:388)
at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.setProviderFactory(JmsConnectionFactoryImpl.java:170)
at com.ibm.mq.jms.MQConnectionFactory.<init>(MQConnectionFactory.java:240)
at com.ibm.mq.jms.MQQueueConnectionFactory.<init>(MQQueueConnectionFactory.java:76)
at com.ibm.mq.jms.MQXAQueueConnectionFactory.<init>(MQXAQueueConnectionFactory.java:69)
at com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory.getObjectInstance(MQXAQueueConnectionFactoryFactory.java:77)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
As you can see weblogic complains about com.ibm.mq.jmqi.system.JmqiComponent, I googled JmqiComponent but dose not exists which is strange :P. Has anybody what is a reason for such a behaviour.

Hello.
I would ditch the foreign JMS approach. There is a detailed example of how to use the resource adapter for the same goal here:
WebSphere MQ resource adapter and Weblogic - how?
While Oracle supports foreign JMS, IBM won't. The only pattern that both IBM and Oracle support is resource adapter.
Let me know, if you need more guidance.
-Adrian

Similar Messages

Inqmy resource adapter for SAP with Bea Weblogic Server

 Hi everybody,
 Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic server
 It works well with INQMY server, but with BEA I'm getting a lot of problems creating
 the connections.
 Thanks in advance.
 Xavi.


All,
 Here are the steps we (used for internal testing) had to perform to get
 IN-Q-MY adapter for SAP to work with WebLogic:
 The wli.adapter.inqmy.sapr3.spi package contains extensions to the
 In-Q-My J2EE Connector Architecture classes to overcome some limitations
 in the base implementation classes. To get around these issues, we had
 to extend their R3ManagedConnectionFactory, R3ConnectionManager, and
 R3ConnectionFactory classes.
 * The javax.resource.spi.ManagedConnectionFactory implementation
 does not over-ride the equals and hashCode methods correctly. This
 causes problems with WLS 6.1.
 * There is a bug in their javax.resource.spi.ConnectionManager
 implementation for non-managed uses of the adapter. Consequently, their
 adapter cannot be used in a non-managed scenario.
 * The javax.resource.cci.ConnectionFactory class does not support
 the getConnection() method that does not take any arguments (it throws a
 null pointer exception).
 I am attaching the classes discussed above.
 Cheers,
 Chris
 Torsten Friebe wrote:
 > Hi,
 >
 > does anybody know where to get a trail version - if one exists - of IN-Q-MY
 > application server or the resource adapter?
 >
 > Thanks, regards
 > Torsten
 >
 > "Xavi" <[email protected]> schrieb im Newsbeitrag
 > news:[email protected]...
 >
 >>Hi everybody,
 >>
 >>Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic
 >>
 > server
 >
 >>?
 >>
 >>It works well with INQMY server, but with BEA I'm getting a lot of
 >>
 > problems creating
 >
 >>the connections.
 >>
 >>Thanks in advance.
 >>Xavi.
 >>
 >>
 >
 >
 package wli.adapter.inqmy.sapr3.spi;
 import java.io.Serializable;
 import javax.resource.ResourceException;
 import javax.resource.cci.Connection;
 import javax.resource.cci.ConnectionSpec;
 import javax.resource.spi.ConnectionManager;
 import javax.resource.spi.ConnectionRequestInfo;
 import javax.resource.spi.ManagedConnection;
 import javax.resource.spi.ManagedConnectionFactory;
 import com.inqmy.r3adapter.R3ConnectionSpec;
 import com.inqmy.r3adapter.R3ManagedConnectionFactory;
 * Extends the In-Q-My implementation to allow for getConnection() with no
 * connection spec, i.e. use the default configured connection parameters.
 public class R3ConnectionFactory
 extends com.inqmy.r3adapter.R3ConnectionFactory
 implements com.bea.connector.IProxyMarker {
 private R3ConnectionSpec m_cspec;
 public R3ConnectionFactory(ConnectionManager cm, R3ManagedConnectionFactory mcf)
 throws ResourceException {
 super(cm, mcf);
 String strClientNumber = mcf.getClientNumber();
 if (strClientNumber == null) {
 throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+mcf);
 String strLanguage = mcf.getLanguage();
 if (strLanguage == null) {
 throw new javax.resource.spi.IllegalStateException("Language not set for "+mcf);
 String strUserName = mcf.getUserName();
 if (strUserName == null) {
 throw new javax.resource.spi.IllegalStateException("UserName not set for "+mcf);
 String strPassword = mcf.getPassword();
 if (strPassword == null) {
 throw new javax.resource.spi.IllegalStateException("Password not set for "+mcf);
 m_cspec = new R3ConnectionSpec(strClientNumber, strLanguage, strUserName, strPassword);
 public Connection getConnection(ConnectionSpec connectionSpec)
 throws ResourceException {
 if (connectionSpec == null) connectionSpec = m_cspec;
 return super.getConnection(connectionSpec);
 package wli.adapter.inqmy.sapr3.spi;
 import java.io.Serializable;
 import javax.resource.ResourceException;
 import javax.resource.spi.ConnectionManager;
 import javax.resource.spi.ConnectionRequestInfo;
 import javax.resource.spi.ManagedConnection;
 import javax.resource.spi.ManagedConnectionFactory;
 * Extends the In-Q-My implementation to over-ride the
 * allocateConnection method to return a CCI connection vs. a ManagedConnection
 public class R3DefaultConnectionManager
 implements ConnectionManager, Serializable {
 public R3DefaultConnectionManager() {}
 public Object
 allocateConnection(ManagedConnectionFactory mcf, ConnectionRequestInfo cri)
 throws ResourceException {
 ManagedConnection mc = mcf.createManagedConnection(null, cri);
 return mc.getConnection(null, cri);
 package wli.adapter.inqmy.sapr3.spi;
 import javax.resource.spi.ConnectionManager;
 import javax.resource.spi.ConnectionRequestInfo;
 import javax.resource.spi.ManagedConnection;
 import javax.security.auth.Subject;
 * Extends the In-Q-My implementation to get around some problems encountered
 * while running on WebLogic:
 * <ul>
 * <li>Must over-ride default implementation of equals and hashCode method</li>
 * <li>Needed to provide my version of the CCI ConnectionFactory</li>
 * <li>Needed to provide my version of the default ConnectionManager for the
 * non-managed scenario use case</li>
 * </ul>
 public class R3ManagedConnectionFactory
 extends com.inqmy.r3adapter.R3ManagedConnectionFactory {
 private int m_iHashCode;
 transient private com.inqmy.r3adapter.R3ConnectionRequestInfo t_cri = null;
 public R3ManagedConnectionFactory() {
 super();
 java.rmi.server.UID uid = new java.rmi.server.UID();
 m_iHashCode = uid.hashCode();
 public Object createConnectionFactory() {
 // need to install our own default connection manager because In-Q-My
 // version causes a ClassCastException in CCI ConnectionFactory
 // getConnection
 return createConnectionFactory(new R3DefaultConnectionManager());
 public ManagedConnection createManagedConnection(Subject subject, ConnectionRequestInfo cri)
 throws javax.resource.ResourceException {
 // need to check for null on the ConnectionRequestInfo object because the
 // In-Q-My R3ManagedConnection ctor does not check for null
 if (cri == null) cri = getDefaultConnectionRequestInfo();
 return new com.inqmy.r3adapter.R3ManagedConnection(this, subject, cri);
 public Object createConnectionFactory(ConnectionManager connectionManager) {
 // need to supply a connection factory that can deal with getConnection
 // that does not take a ConnectionSpec
 try {
 return new R3ConnectionFactory(connectionManager, this);
 } catch (javax.resource.ResourceException re) {
 re.printStackTrace();
 throw new java.lang.IllegalStateException(re.getMessage());
 com.inqmy.r3adapter.R3ConnectionRequestInfo getDefaultConnectionRequestInfo()
 throws javax.resource.spi.IllegalStateException {
 if (t_cri == null) {
 String strClientNumber = this.getClientNumber();
 if (strClientNumber == null) {
 throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+this);
 String strLanguage = this.getLanguage();
 if (strLanguage == null) {
 throw new javax.resource.spi.IllegalStateException("Language not set for "+this);
 String strUserName = this.getUserName();
 if (strUserName == null) {
 throw new javax.resource.spi.IllegalStateException("UserName not set for "+this);
 String strPassword = this.getPassword();
 if (strPassword == null) {
 throw new javax.resource.spi.IllegalStateException("Password not set for "+this);
 t_cri = new com.inqmy.r3adapter.R3ConnectionRequestInfo(strClientNumber, strLanguage, strUserName, strPassword);
 return t_cri;
 public boolean equals(Object obj) {
 if (obj == null) return false;
 if (obj == this) return true;
 if (!this.getClass().isInstance(obj)) return false;
 R3ManagedConnectionFactory mcf = (R3ManagedConnectionFactory)obj;
 return compare(getClientNumber(), mcf.getClientNumber()) &&
 compare(getLanguage(), mcf.getLanguage()) &&
 compare(getUserName(), mcf.getUserName()) &&
 compare(getPassword(), mcf.getPassword()) &&
 compare(getServerName(), mcf.getServerName()) &&
 compare(getSystemNumber(), mcf.getSystemNumber());
 protected final boolean compare(final Object obj1, final Object obj2) {
 if (obj1 == obj2) return true;
 if (obj1 != null) {
 return obj1.equals(obj2);
 } else {
 if (obj2 == null) {
 return true;
 } else {
 return false;
 public int hashCode() { return m_iHashCode; }

Build and run Sun's PetStore1.3.1_02 application with BEA WebLogic Server 8.1.

build and run Sun's PetStore
1.3.1_02 application with BEA WebLogic Server 8.1.
5) In the same Command Prompt, compile PetStore using the commands:
cd c:\bea\user_projects\domains\petstore
setPetStoreEnv.cmd
cd c:\petstore1.3.1_02\src
ant
buildfile:build.xml does not exist!
build failed
could you tell me how ?
thank you

What we, BEA, provides is a patch to allow you to compile Pet Store for
WebLogic Server. It does not contain the source code.
Sun's Pet Store source code can be found at
http://developer.java.sun.com/developer/releases/petstore/petstore1_3_1_02.h
tml. See the requirements section of README.TXT
You need both in order to make it work.
"Ankur" <[email protected]> wrote in message
news:3fa9f2d9$[email protected]..
Hi Nick,
I tried building the petstore1.3.1_02 application following theinstructions in the readme. But I got an error as the buil.xml file is
missing in the directory.....\petstore1.3.1_02\src.
>
I tried unzipping the downloaded again and for a petstore.domain.jar alongwith the readme. This jar does not contain the build.xml file.
>
Then I tried compiling one by one the component folder and found that the../xmldocuments/src folder has only a build.xml file but no source file...
>
Kinldy suggest what to do? Can you send me the zip via email?
P.S: I have checked the zip and the files are missing.

Bea Weblogic server 10.3

how to make a call with bea weblogic server 10.3?

A 'call'? Surely you have more definition than that.
http://www.oracle.com/technology/documentation/bea.html gives a bit of a start.

Is the 11.1.1.2 software compatible with BEA WebLogic 10.3?

Hi,
Does anyone know, is Oracle EPM version 11.1.1.2 compatible with BEA WebLogic 10.3? I know the recommended version is 9.2 MP3 for Windows 32 bit.
Do we need to get seperate license for WebLogic or is it included in this EPM software bundle?
Thanks for your answers in advance..!

Not sure about the licensing, its best to ask someone at Oracle, but I believe when you when automatic deploy 11.1.1.2 apps to Oracle10gR3 Application Server, it is actually referring to the Oracle Weblogic 10.3 Application Server, not the old Oracle (OAS) 10G Application Server, so it should work. You can also deploy to Weblogic 9.2 and IBM Webshpere automatically. I believe all other application servers may still be compatible but require a manual deployment.
Regards,
Imran

Crystal Reports in Java with BEA Weblogic (test drive)

Hello, 
 
The question is: What is wrong with Crystal Reports or BEA Weblogic, when they are working together? And how can it be repaired? 
 
I have a project working with reports. Tried to implement it for crystal reports and found an interesting problem. Crystal Reports didn't work with BEA Weblogic as well as with other servers. 1-2 years ago we just took Tomcat and worked with it. Right now we are interested in working with BEA. 
 
Everything works, but much slower than other servers. The best explanation is just a my tries in the end of the post. I hope some clever man helps me to option Weblogic or at least explains what is wrong. 
 
Test results are: 
 
- Apache Software Foundation - Tomcat 6.0: 
~3 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~1 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
- OC4J - Oracle Containers for J2EE 10g (10.1.3.3.0): 
~4 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~1 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
- Jetty 7.0.0.pre5: 
~2 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~0 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
- BEA Weblogic 9.2: 
~30 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~8 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
simple_cr_webapp.war (30 MB) can be downloaded [here|http://rapidshare.com/files/221096566/simple_cr_webapp.war.html] or [here|http://math.ut.ee/~a30858/simple_cr_webapp.war]: 
crystalreportviewers //all viewers for 2.0
WEB-INF
classes
CRConfig.xml //see WAR - without key, only sets timeout and report location
lib //all libraries for Eclipse plugin's web-app + j2ee.jar
web.xml //see WAR - generated by Eclipse plugin
sample.jsp //see WAR - generated by Eclipse plugin
sample.rpt //"Consolidated Balance Sheet.rpt" from Eclipse plugin's web-app samples
 
P.S. It is also suites if someone gives a simple project with CR, that works well. I really need to get solution for this problem, so any advises are expected. 

I also tried for different java vendors on BEA Weblogic 9.2.
Results for Jrockit are above: 30 sec and 8 sec
Results for Sun are worse than JRockit: 50 sec and 10 sec
JRockit:
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
BEA JRockit(R) (build R26.0.0-189_CR269406-59389-1.5.0_04-20060322-1120-win-ia32, )
JAVA Memory arguments: -Xms500m -Xmx1000m
Sun:
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m

Problem in running application(using ADF) on BEA Weblogic Server

Hi..,
I am Gunardy Sutanto from Indonesia. Currently, I had a problem in deploying application which is using ADF framework in BEA Weblogic Server(WLS 8.1). I also add all the libraries which were required for running this application. But I found some error when I ran this application. About the error message that I found from log file which is generated by BEA Weblogic Server 8.1, herewith I attach the detail of the error message :
<Error> <HTTP> <BEA-101020> <[ServletContext(id=27825828,name=bp_presentment,context-path
=/bp_presentment)] Servlet failed with Exception
oracle.jbo.PCollException: JBO-28030: Could not insert row into table PS_TXN, collection id 16,408, persistent id 1
at oracle.jbo.PCollException.throwException(PCollException.java:39)
at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1845)
at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
## Detail 0 ##
java.lang.ClassCastException
at oracle.jbo.pcoll.OraclePersistManager.updateBlobs(OraclePersistManager.java:1613)
at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1832)
at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
I hope this is enough for somebody for solving this problem. If someone have the solution for this problem, please contact me by e-mail to [email protected].
Thanks,
Gunardy

I already set the value for jbo.server.internal_connection and then deployed to Weblogic Server. When I was tested the application, all the records from table had shown on the screen but I found the application can't insert row to table PS_TXN. I I want to know it always happened?
Herewith I attach the detail log from log file which was generated by Weblogic Server:
oracle.jbo.PCollException: JBO-28030: Could not insert row into table PS_TXN, collection id 162, persistent id 1 at oracle.jbo.PCollException.throwException(PCollException.java:39)
 at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1845)
 at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
 at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
 at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
 at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
 at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
 at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
 at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
 at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
 at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
 at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
 at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
 at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
 at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
 at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
 at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
 at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
 at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
 at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
## Detail 0 ##
java.lang.ClassCastException
 at oracle.jbo.pcoll.OraclePersistManager.updateBlobs(OraclePersistManager.java:1613)
 at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1832)
 at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
 at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
 at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
 at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
 at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
 at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
 at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
 at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
 at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
 at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
 at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
 at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
 at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
 at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
 at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
 at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
 at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
 at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Besides that, I found new error when I was starting Weblogic Server. Herewith, I attach the detail of the error message:
java.lang.NoClassDefFoundError: org/apache/commons/collections/FastHashMap$KeySet
 at org.apache.commons.collections.FastHashMap.keySet(Unknown Source)
 at org.apache.struts.action.ActionServlet.destroyDataSources(ActionServlet.java:769)
 at org.apache.struts.action.ActionServlet.destroy(ActionServlet.java:431)
 at weblogic.servlet.internal.ServletStubImpl$ServletDestroyAction.run(ServletStubImpl.java:1086)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:569)
 at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:596)
 at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:581)
 at weblogic.servlet.internal.WebAppServletContext.destroyServlets(WebAppServletContext.java:5797)
 at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:5675)
 at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:187)
 at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:706)
 at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:764)
 at weblogic.servlet.internal.WebAppModule.rollback(WebAppModule.java:742)
 at weblogic.j2ee.J2EEApplicationContainer.rollbackModule(J2EEApplicationContainer.java:2942)
 at weblogic.j2ee.J2EEApplicationContainer.rectifyClassLoaders(J2EEApplicationContainer.java:1429)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1176)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
So, I need someone to sove this problem. I am looking forward for hearing from you.
Thanks,
Gunardy

Trouble defining BAM Enterprise Message Source for BEA WebLogic Server

Hi all,
I've just started to play a little with Oracle BAM Architect.
I've WLS 10.0 and Oracle BAM Architect 10g release 3.
On Oracle BAM Architect I've defined an Enterprise Message Source for BEA WebLogic Server as follows:
Name: ALSBSource
Owner: ...
Type: BEA WebLogic Server
Initial context factory: weblogic.jndi.WLInitialContextFactory
JNDI Service Provider URL: t3://mypc:7001
TopicConnectionFactory name: com.myConnectionFactory
Topic name: com.myBAMTopic
JMS message type: TextMessage
Durable subscriber name: BAMSubscriber
Client ID: BAMSubscriber
Name | Flow name | Type | Max size | Formatting
content | BAM | String | 1024 | (none)
On WLS 10.0 I've defined the required JMS stuff.
On Oracle Design Studio I've defined a plan that includes:
- an Oracle BAM Enterprise Message Receiver from which I've selected the above 'ALSBSource' Enterprise Message Source
- a simple Grid
I've connected the BAM Enterprise Message Receiver to the Grid and clicked on 'Update' button.
When I try to publish a message on 'com.myBAMTopic' I don't see anything on the grid defined in the Oracle Design Studio.
The first question is about the definition of an Enterprise Message Source for BEA WebLogic Server in the Oracle BAM Architect.
I did not change the Oracle BAM Architect classpath or Oracle Design Studio classpath adding the weblogic.jar, because no error has been raised during the configuration of the message source and the plan. Should I update Oracle classpath with the weblogic.jar ?
Did I forget any other step ?
I thank you in advance for any feedback.
Regards
ferp

ferp - I got this to work with
JNDI Service Provider URL: http://localhost
When I add the port
JNDI Service Provider URL: http://localhost:23891
I cannot get my EMS to start.
Hopefully this should fix your issue.
Sudeep.

Error Configuring BEA Weblogic Server v9.2

I'm using Eclipse 3.4 (Ganymede) with the new Enterprise Pack for Eclipse. When I try to create a New Server Runtime Environment for Weblogic 9.2, I get the following error:
"RE is selected, but the path is invalid."
The path is D:\export\webapps\sbea\weblogic92 which is correct because I successfully used that with Eclipse 3.3 with BEA Weblogic Weblogic 9.2 runtime that you could access from Eclipse 3.3.

I was able to fix this by uninstalling all BEA products and re-installing WLS 9.2M1.

An internal error occurred during: "Starting BEA WebLogic Server v8.1 at lo

Hi,
On "Start the server in debug mode"
file .log
eclipse.buildId=I20090611-1540
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_AR
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.core.jobs 4 2 2009-08-05 12:29:57.060
!MESSAGE An internal error occurred during: "Starting BEA WebLogic Server v8.1 at localhost".
!STACK 0
java.lang.NullPointerException
     at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.findWorkshopJspDebuggerLaunchConfigurationDelegate(GenericWeblogicServerBehaviour.java:477)
     at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.setupLaunch(GenericWeblogicServerBehaviour.java:226)
     at org.eclipse.jst.server.generic.core.internal.ExternalLaunchConfigurationDelegate.launch(ExternalLaunchConfigurationDelegate.java:101)
     at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
     at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
     at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
     at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3057)
     at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3007)
     at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:294)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
OS= Windows XP SP2
Eclipse Java Version= 1.6.0_13
Workspace Java Version= 1.4.2_08
BEA Weblogic= 8.1.6
Eclipse= 3.5.0
WTP= 3.1.0
Project Facets= Dynamic Web Module 2.3
Java= 1.4
Tanks and sorry my English.
Gustavo

I am also experiencing the same NullPointerException when launching Weblogic 8.1 in debug mode within Eclipse 3.5. Is there any anticipated fix for this issue, or a bugtraq record that we can follow to know when the issue is addressed? I do not expect JSP debugging to work (as it wasn't available with Weblogic 8.1 under Eclipse 3.4 either) - BUT right now I cannot debug ANY server-side code within Weblogic 8.1 in Eclipse 3.5 as the server cannot start in debug mode at all.
Many thanks.

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
We are very excited about this beta program and appreciate your
participation. In the past, our public betas have been very well received
by our developer community. So, we have once again organized a public beta
program to enable everyone to preview our latest release.
We do ask that you follow a few guidelines:
-- There will be no voice, e-mail, or fax support for this beta through the
technical support organization. All questions, bug reports, or comments on
the beta program should be directed to to the WebLogic beta newsgroups at
news://newsgroups.bea.com. These newsgroups are:
weblogic.developer.interest.60beta.transaction
weblogic.support.install.60beta
weblogic.developer.interest.60beta.ejb
weblogic.developer.interest.60beta.clustering
weblogic.developer.interest.60beta.security
weblogic.developer.interest.60beta.jdbc
weblogic.developer.interest.60beta.jms
weblogic.developer.interest.60beta.performance
weblogic.developer.interest.60beta.misc
weblogic.developer.interest.60beta.servlet
weblogic.developer.interest.60beta.jsp
weblogic.developer.interest.60beta.tools
weblogic.developer.interest.60beta.rmi-iiop
weblogic.developer.interest.60beta.management
weblogic.developer.interest.60beta.management.console
weblogic.developer.interest.60beta.management.general_and_jmx
weblogic.developer.interest.60beta.internationalization
weblogic.developer.interest.60beta.xml
weblogic.developer.interest.60beta.jndi
weblogic.developer.interest.60beta.documentation
weblogic.developer.interest.60beta.javamail
-- Please remember that this release is currently beta code. This means that
it should not be put into production deployments until the final release
occurs.
-- It is very likely that this release will contain bugs and errors. This is
the nature of beta code. Please the patient with us as we do our best to fix
any problems that we find. We will do our absolute best to make sure that
your issues are addressed as soon as possible.
-- Please do not post any issues relevant to the beta on the standard
newsgroups also available at news://newsgroups.bea.com.
-- Please use the newsgroup for all communication and do not contact any BEA
employees directly. They have been instructed to direct you to comment only
via the newsgroup.
-- Please review previous posts in the newsgroups before posting. If you
locate a bug or need to ask a question, it is very likely that it will have
been asked before.
-- Please do not post on the newsgroup using hostile or profane language.
Inappropriate posts will be removed and offenders will be blocked from the
beta program.
Thank you again for your support and participation. We very much appreciate
all that you will be doing to make this release of the BEA WebLogic Server
as great as possible.
Michael Girdley
BEA Systems Inc

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
We are very excited about this beta program and appreciate your
participation. In the past, our public betas have been very well received
by our developer community. So, we have once again organized a public beta
program to enable everyone to preview our latest release.
We do ask that you follow a few guidelines:
-- There will be no voice, e-mail, or fax support for this beta through the
technical support organization. All questions, bug reports, or comments on
the beta program should be directed to to the WebLogic beta newsgroups at
news://newsgroups.bea.com. These newsgroups are:
weblogic.developer.interest.60beta.transaction
weblogic.support.install.60beta
weblogic.developer.interest.60beta.ejb
weblogic.developer.interest.60beta.clustering
weblogic.developer.interest.60beta.security
weblogic.developer.interest.60beta.jdbc
weblogic.developer.interest.60beta.jms
weblogic.developer.interest.60beta.performance
weblogic.developer.interest.60beta.misc
weblogic.developer.interest.60beta.servlet
weblogic.developer.interest.60beta.jsp
weblogic.developer.interest.60beta.tools
weblogic.developer.interest.60beta.rmi-iiop
weblogic.developer.interest.60beta.management
weblogic.developer.interest.60beta.management.console
weblogic.developer.interest.60beta.management.general_and_jmx
weblogic.developer.interest.60beta.internationalization
weblogic.developer.interest.60beta.xml
weblogic.developer.interest.60beta.jndi
weblogic.developer.interest.60beta.documentation
weblogic.developer.interest.60beta.javamail
-- Please remember that this release is currently beta code. This means that
it should not be put into production deployments until the final release
occurs.
-- It is very likely that this release will contain bugs and errors. This is
the nature of beta code. Please the patient with us as we do our best to fix
any problems that we find. We will do our absolute best to make sure that
your issues are addressed as soon as possible.
-- Please do not post any issues relevant to the beta on the standard
newsgroups also available at news://newsgroups.bea.com.
-- Please use the newsgroup for all communication and do not contact any BEA
employees directly. They have been instructed to direct you to comment only
via the newsgroup.
-- Please review previous posts in the newsgroups before posting. If you
locate a bug or need to ask a question, it is very likely that it will have
been asked before.
-- Please do not post on the newsgroup using hostile or profane language.
Inappropriate posts will be removed and offenders will be blocked from the
beta program.
Thank you again for your support and participation. We very much appreciate
all that you will be doing to make this release of the BEA WebLogic Server
as great as possible.
Michael Girdley
BEA Systems Inc

Bea weblogic server 6.1 - Failure in process sockets - Java.lang.NoSuchmethod Error

Hi
I have installed the BEA weblogic server 6.1 service pack 4 as part of PIA (PeopleSoft
Internet Architecture) installation for PeopleSoft 8.8.
After starting the weblogic server, When I type the
http://localhost:12080 (http port number 12080) ideally it should take me to
the BEA home page, but it is throwing an error in the log file.
" Failure in Process sockets - Get Data Java.lang.nosuchmethod error"
Your help is very much appreciated.
Any pointers are welcome.
Thanks
Aswartha

I had similar problems with my install of Weblogic 6.1 sp4. I am installing PS
HRMS 8.8 sp1
and PeopleTools 8.44 Patch 2 (Patch 2 is required for install) Peoplesoft sent
me Weblogic 8.1
with my new Tools 8.44. This version and installation is light years ahead of
Weblogic 6.1. If
you are able to load the new version of Weblogic and Tuxedo, it is worth it.
If not, you may want to check to see if your JAR file was installed correctly.
(The new version
of WL doesn't make you unzip your JAR files for the install.)
In the command line for unzipping the JAR file, make sure you type the phrase
EXACTLY as
shown IT IS CASE SENSITIVE. I messed with this for two hours until I saw that
I wasn't putting
a capital letter in one of the words where I should have been.
Hope this helps.
"Aswarth" <[email protected]> wrote:
>
Hi
I have installed the BEA weblogic server 6.1 service pack 4 as part of
PIA (PeopleSoft
Internet Architecture) installation for PeopleSoft 8.8.
After starting the weblogic server, When I type the
http://localhost:12080 (http port number 12080) ideally it should take
me to
the BEA home page, but it is throwing an error in the log file.
" Failure in Process sockets - Get Data Java.lang.nosuchmethod error"
Your help is very much appreciated.
Any pointers are welcome.
Thanks
Aswartha

[BEA WEBLOGIC SERVER 5.1 sp8] performance pack load problem ....

Hi,
I am trying to use the weblogic server performance pack on BEA WEBLOGIC SERVER 5.1
sp8.
As explained in the following doc : http://www.weblogic.com/docs51/admindocs/tuning.html#performance%20packs
I use the following configuration :
weblogic.properties : weblogic.system.nativeIO.enable=true
LD_LIBRARY_PATH is set to "/bea/weblogic/wls510_sp8/lib/solaris"
Technical environement : SunOS 5.8 Generic_108528-06
But when I restart the server I have the following message :
"Mo Jun 03 18:19:06 CEST 2002:<A> <Posix Performance Pack> Could not initialize POSIX
Performance Pack.
Mo Jun 03 18:19:06 CEST 2002:<E> <Performance Pack> Unable to load performance pack,
using Java I/O."
Could you help me on this point, please ?

I think my Q is not clear. I shall explain how the application works. I am having application based on Swings and that is a website building program. User has options like ading an image into their site with an element called 'Image' available as part of the system. Then user can either select an image from the picture gallery provided or can upload his own image.
Now, if the user is uploading a picture that has space in name ( we use a servlet program to upload the image into user directory), it will get uploaded. But when the swing program tries to paint the image in the Image element ( It is essentially a JLabel ), the program is sending a request to the WL server. Since the URL contains space in name, server returns error. Even if do URL Encoding, it will add %20 in the URL and still WL will report error saying that file not found. It seems that WL is unable to process requests that has space in the URL.
If any one has any solution to this, please help..
Liju

Installing Oracle SOA Suite with the WebLogic Server

Hi all,
I am trying to install Oracle SOA Suite with the WebLogic Server. After following the step-by-step instruction in the "Installing Oracle SOA Suite with the WebLogic Server" document, I ran into the following situation: I have a working WebLogic Server with all applications deployed. However the BPELPM application is in Failed state.
When I try to run the application, I get following exception (AdminServer.log):
####<Mar 30, 2009 9:46:43 AM EEST> <Warning> <Deployer> <javadev2> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238395603163> <BEA-149004> <Failures were detected while initiating start task for application 'BPELPM'.>
####<Mar 30, 2009 9:46:43 AM EEST> <Warning> <Deployer> <javadev2> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238395603164> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101216]Servlet: "cxloader" failed to preload on startup in Web application: "/orabpel".
javax.servlet.ServletException:
ORABPEL START-UP ERROR!!!!!!!!
OraBPEL run-time system failed to start due to exception:
Bean is already undeployed.
at com.collaxa.cube.admin.CXLoaderServlet.init(CXLoaderServlet.java:87)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:278)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1723)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1700)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1620)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2761)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Any help would be highly appreciated.
Boris

Hi Boris,
Looks like you have not run the post upgrade script for 10.1.3.4.
You need to install SOA 10.1.3.4 Basic Installation. Then start following : http://download.oracle.com/docs/cd/E12524_01/core.1013/e13058/weblogic.htm#BHCIIBFB
You basically, first install 10.1.3.4 basic SOA install, Apply the Opatch 7337034 (HOTPLUG: SOASUITE 10.1.3.4 ON WEBLOGIC 9.2 - CHANGES FOR HOTPLUGGABILITY). Install WLS 9.2 MP3.
Now, Download the Oracle SOA Suite 10.1.3.4 WebLogic Server 9.2 : patch : 7490612.
Then , Modify the following mandatory installation properties in the Weblogic_SOA10134_Base\SOADomain.properties file as per the documentation above.
Cheers
Anirudh Pucha

Bea Weblogic Server performance question.

Hello,
Im wondering if there are big performance difference between Bea Weblogic Server
versions.
I run BWS 5.1 and find it great, I ve tested the application on 6.0 and it seems
to run as good as 5.1, I ve tested with 6.1 and it works fine too.
And now is my question... is it big difference between WLS from 5.1, 6.0, 6.1,
7.0, 8.0, 8.1 ???
I dont need any "super-hyper" features just run a simple EJB (30-40 EJBs) application.
If there are big performance difference then there is a good reason to update
to the latest WLS. (Do you have any benchmark urls for this issue?)
Do I need to modify the EJBs if I want to upgrade from 5.1 to 8.1 ??
When I upgraded from 5.1 to 6.1 there was a little changes I ve to make in the
xml files.
Thanks for all your help!
/Sonny!

"Sonny" <[email protected]> wrote in message
news:3f0d6ca6$[email protected]..
|
| Hello,
|
| Im wondering if there are big performance difference between Bea Weblogic
Server
| versions.
| I run BWS 5.1 and find it great, I ve tested the application on 6.0 and it
seems
| to run as good as 5.1, I ve tested with 6.1 and it works fine too.
| And now is my question... is it big difference between WLS from 5.1, 6.0,
6.1,
| 7.0, 8.0, 8.1 ???
| I dont need any "super-hyper" features just run a simple EJB (30-40 EJBs)
application.
|
| If there are big performance difference then there is a good reason to
update
| to the latest WLS. (Do you have any benchmark urls for this issue?)
|
| Do I need to modify the EJBs if I want to upgrade from 5.1 to 8.1 ??
| When I upgraded from 5.1 to 6.1 there was a little changes I ve to make in
the
| xml files.
|
| Thanks for all your help!
|
| /Sonny!
As new versions release, there is differences in performance. One
significant point to note is the JVM versions that are supported which
significantly impact the application server performance. The new WLS 8.1 on
the newest released 1.4.2 JVM is damn good. The 1.4.1_0x JVMs have been
dramatically slower in tests that I've done. So even incremental releases
will make an impact.
In newer releases, code matures also. I also believe in 7.x they gave the
capability of clustering JVM more effectively.
anyway... good luck.
ken k

Integrating WebSphere MQ 5.3 with BEA Weblogic Server 9.2 3M

Similar Messages

Maybe you are looking for