WebLogic Integration eval fails installation
I installed WebLogic 6.0 SP2 and the EJB 2.0 Upgrade as told in the installation
document, but the Integration Installer fails giving the message "No existing
Weblogic" and exists.
Does anybody had this problem before ?
regards,
Linus
I would, but there doesn't seem to be a group like that on
newsgroups.bea.com...
Linus
"Chuck" <[email protected]> schrieb im Newsbeitrag
news:3bc5f959$[email protected]..
>
Linus,
I would post this message in the weblogic.integration.install newsgroupsince
the problem is related to the Integration Installer and not the WebLogicServer
installer
Similar Messages
-
Weblogic Integration 2.0 fails to install on Win2000
Hi,
I was installing Weblogic Integration 2.0 (eval copy) on Windows 2000. The first
component which got installed was the Process Integrator 2.0 piece. I chose Cloudscape
for the database. All other inputs were default values. At the end of the installation,
the installer came up with a message that it did not install properly. The install
errors text file tells me that there was a runtime error during Cloudscape db
creation. (listed below)
Does anyone have an idea what the problem could be? Any kind of input would be
helpful.
Thanks
Karthik.
contents of installErrors.txt file:
Jul 12, 2001 5:13:19 PM -- Error During The "Cloudscape" database creation. --
Runtime exec failed.Karthik,
We also got this error installing WebLogic Integration 2.0 on a Windows 2000 machine.
It seems that the Cloudscape initialisation fails if you are installing to a directory
with spaces anywhere in the path. After changing our target path from c:\program
files\etc... to c:\wli20\etc... the installation concluded successfully.
Hope this helps.
Edward Wichmann
Perpsective Technologies
WebLogic Consulting available in the UK
Tel: +44 (0)7866 425774
E-mail: [email protected]
"Karthik Krishnamoorthy" <[email protected]> wrote:
>
Hi,
I was installing Weblogic Integration 2.0 (eval copy) on Windows 2000.
The first
component which got installed was the Process Integrator 2.0 piece. I
chose Cloudscape
for the database. All other inputs were default values. At the end of
the installation,
the installer came up with a message that it did not install properly.
The install
errors text file tells me that there was a runtime error during Cloudscape
db
creation. (listed below)
Does anyone have an idea what the problem could be? Any kind of input
would be
helpful.
Thanks
Karthik.
contents of installErrors.txt file:
Jul 12, 2001 5:13:19 PM -- Error During The "Cloudscape" database creation.
Runtime exec failed. -
Weblogic Integration failed to build Cluster ENV
Dear buddies,
I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
Here is the process how I created WLI cluster:
ENV:RedHat9+ WL8.1_SP4
Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
BEA_HOME=/opt/bea/
1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
and I didn't create extra JDBC POOL except the standard one.
2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
Now I am having following problem.
1.admin Server(cgServer) can startup without any problem
2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
but seems the pointbase only listen 9092!!
4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
below are detailed output when I startManagedServers:
command:
[root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
Listen Address 172.16.4.236:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.
-
Bea Weblogic Integration 9.2 Unix installer
Hi
Can somebody please help me to get Bea Weblogic Integration 9.2 Unix installer ? I want it for developement purpose on unix machine.
I am not able to find it on the oracle product site.
Thank you.There is one link here - not sure if it is the one you need
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
HTH
Srini -
Integration 10g silent installation will not install WebLogic Workshop
Hello,
I am attempting a silent installation, using wli10gR3_win32.exe. I have created a silent.xml using the information on this page: http://download.oracle.com/docs/cd/E13214_01/wli/docs85/install/silent.html.
I have used that page in the past to successfully create silent installations for versions 8 and 9 of Weblogic, but for version 10g it is not quite working as advertised. I have not found instructions for a silent installation for 10g.
My silent.xml file contains the following line:
<data-value name="COMPONENT_PATHS" value="WebLogic Server|WebLogic Workshop|WebLogic Integration|WebLogic Portal" />
When I run the package with this line, an error is produced in the log file stating that WebLogic Workshop cannot be found.
When I remove the WebLogic Workshop part of the line then Server, Integration, and Portal all install without errors. Unfortunately, Workshop was requested as well.
When I run the installation manually, I am offered Workshop as one of the products.
If somebody can point me to the correct installation documentation or provide the correct syntax for the silent.xml file that would be swell.
thanks.Hi,
I had faced the same issue today, So I had removed workshop and the installation was successful. But the weird thing is after the installation I could see the "workshop" was installed under BEA_HOME.
Did any one face the same issue?
Thanks.
Vijay Bheemineni. -
BPM for Weblogic configuration is failed
1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) 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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) 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.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?Hi,
Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
-------------------log message-------------------------------
TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
TO_MSG
TO_MSG Your environment has been set.
TO_MSG
TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
TO_MSG
TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
TO_MSG
TO_MSG Welcome to WebLogic Server Administration Scripting Shell
TO_MSG
TO_MSG Type help() for help on available commands
TO_MSG
TO_MSG Starting server BPMServer
TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
TO_MSG Starting weblogic server ...
TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ26¥ネニ58ᄃメ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ00ᄃメ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ00ᄃメ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ12ᄃメ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ13ᄃメ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ15ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ15ᄃメ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ16ᄃメ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ24ᄃメ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ34ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ34ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ34ᄃメ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35ᄃメ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35ᄃメ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ36ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ36ᄃメ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
TO_MSG Server started successfully.
TO_MSG Started Server. Trying to connect to the server ...
TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
TO_MSG
TO_MSG Warning: An insecure protocol was used to connect to the
TO_MSG server. To ensure on-the-wire security, the SSL port or
TO_MSG Admin port should be used instead.
TO_MSG
TO_MSG Location changed to edit tree. This is a writable tree with
TO_MSG DomainMBean as the root. To make changes you will need to start
TO_MSG an edit session via startEdit().
TO_MSG
TO_MSG For more help, use help(edit)
TO_MSG
TO_MSG Starting an edit session ...
TO_MSG Started edit session, please be sure to save and activate your
TO_MSG changes once you are done.
TO_MSG creating mbean of type JMSServer ...
TO_MSG creating mbean of type JMSSystemResource ...
TO_MSG creating mbean of type SubDeployment ...
TO_MSG creating mbean of type Queue ...
TO_MSG creating mbean of type Topic ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type Server ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Realm ...
TO_MSG creating mbean of type RoleMapper ...
TO_MSG creating mbean of type CredentialMapper ...
TO_MSG creating mbean of type CertPathProvider ...
TO_MSG creating mbean of type Authorizer ...
TO_MSG creating mbean of type Adjudicator ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG setting attributes for mbean type JMSServer
TO_MSG setting attributes for mbean type JMSSystemResource
TO_MSG setting attributes for mbean type SubDeployment
TO_MSG setting attributes for mbean type Queue
TO_MSG setting attributes for mbean type Topic
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type Server
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type DefaultIdentityAsserter
TO_MSG setting attributes for mbean type SecurityConfiguration
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type EmbeddedLDAP
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type Domain
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type JDBCXAParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG Saving all your changes ...
TO_MSG Saved all your changes successfully.
TO_MSG Your edit session is not stopped, you can continue your edits.
TO_MSG Activating all your changes, this may take a while ...
TO_MSG The edit lock associated with this edit session is released
TO_MSG once the activation is completed.
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG
TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
TO_MSG that require server re-start:
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
TO_MSG Attributes changed : ListenAddress
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG Activation completed
TO_MSG Creating a user ...
TO_MSG
TO_MSG Created user successfully
TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ28¥ネニ01ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ28¥ネニ08ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
TO_MSG .................Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ29¥ネニ48ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ30¥ネニ45ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ00ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ31ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ48ᄃメ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ48ᄃメ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
TO_MSG WLST-WLS-1249792014056: at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
TO_MSG WLST-WLS-1249792014056: Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.open(Native Method)
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.<init>(ZipFile.java:117)
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.<init>(ZipFile.java:133)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
TO_MSG WLST-WLS-1249792014056: Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: >
TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.open(Native Method)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.Fil -
Hi all,
I have installed WebLogic Integration 8.5 bundle. Meaning i have also installed weblogic server 8.1. on Windows XP
I am now trying to use Weblogic Scripting Tool WLST. But there is no tools on the menu(tools->weblogic scripting tool) this was added in the 9.1 installation...
How do I configure my installation weblogic server 8.1 with WLI8.5 to run WLST?
after i run setELSEnv.cmd to set the environment. Then i try java weblogic.WLST and the error is "java.lang.NoClassDefFoundError: weblogic/WLST"
Where are the libs, how do i configure WLST to run.
I also tried starting the WLST from the 9.1 installation, but it cannot connect to 8.1 installation, tough connecting to 9.1 installation is no problem. If i try i get this error: "weblogic.management.ManagementRuntimeException: java.lang.NoSuchMethodError: isCachable"
(I installed weblogic 9.1 and there the WLST was installed during installation and all works just fine. unfortenatly my system must run on 8.1->wli8.5)Hi
I am trying to use WLST tool for configuring Weblogic domain in 9.1 OFFLINE.
I have done with almost all except JTA configuration.
Can you please give me smaples for the same.
The following is part iof my script...
readTemplate('F:/AuctionDoc/Installer/inDomain.jar')
cd('/JDBCSystemResource/localNonTxPool/JdbcResource/localNonTxPool')
create('myJdbcDataSourceParams','JDBCDataSourceParams')
cd('JDBCDataSourceParams/NO_NAME_0')
set('JNDIName', 'jdbc/NonTxDataSource')
#JDBC settings and other JMS settings worked
But the JTA settings dint work
#=======================================================================================
# Set JTA timeout
#=======================================================================================
cd("/JTA/inInstDomain")
set("TimeoutSeconds", "1200")
set("AbandonTimeoutSeconds", "1200")
I have to do the above OFFLINE.
I could not locate the JTA folder or any thing related with JTA configuration to do offline using WLST
Can you please give an example of JTA settings
Thanks
Binu -
Upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration
Can anyone offer any advice to assist me in upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration 9.2.1?
Here are some nuances of the project:
* The JNDI, JDBC, & JMS server resources are secured; access is controlled by Deployment Descriptor run-as/security-role/... tags and custom CSPs
* The application is currently build for deployment using wlwBuild ant task (class in workshop.core.WlwBuildTask which is located in the 8.1.3 {weblogic.home}/workshop/wlw-ide.jar - so far I can't find this class/task in my 9.2.1 install)
* The following are the application characteristics (and utilized WLI features): multiple web apps, EJBs, JMS, Page flow/netUI, web services, WLI controls (process, java, transformation), XMLBeans
* One of the project goals is to not make any functional changes and modify as little code as necessary (the only expected justification for a modification is a) fallout out from the JVM 1.5 upgrade or b) something is no longer available in WLI 9.2)
I know there is a edocs page with a tutorial for upgrading from 8.1.4 or 8.1.5 to 9.2, but I am interested in knowing if anyone has insight on upgrading directly from 8.1.3?
Thanks in advance for any and all assistance.
Regards,
Andy Frankjust as a followup to my original message.. regarding the 8.1.4 install log that had all the warnings with the msi it expected and the different one it found... at the bottom of the log..this is what I got;
Property(S): SourcedirProduct = {AC76BA86-7AD7-1033-7B44-A81300000003}
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 - Update 'KB408682' installed successfully.
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 -- Installation operation completed successfully.
when i go into adobe reader -> help -> about i stillget 8.1.3 -
When will WebLogic Integration 9.2 Certification will be available?
Currently it seems only Integration Developer based on WLI 8.1 is available. Since I am using WLI 9.2 not is not suitable.
Anyone know when BEA plan to have WLI 9.2 certification availableT C wrote:
I have also run into the "Run Database Scripts" dialog box after creation of a domain. When I started the domain I got the following error:
<[Security:090737]An exception occured while getting connection to validate the configuration settings
va.sql.SQLException: [Security:090735]The DBMS connection was not usable
I have BEA 9.2 Platform running on Windows 2000 Professional Service pack 3.
Incidentally, I started pointbase manually (startPointBase.cmd), started PointBase Console (startPointBaseConsole.cmd) in order to execute the SQLAuthenticator.sql script. This all failed because this SQL script refers to tables GROUPS and USERS, which did not exist in my PointBase schema.
What worked for me was:
1. Create a new domain, and only select Workshop for WebLogic, WebLogic Portal, and WebLogic Integration options.
2. Select YES to Customize Environment and Services Settings tab.
3. Take defaults until the Run Database Scripts dialog box.
4. On the Run Database Scripts dialog box, run the scripts for p13nDatasource and cgDataSource-nonXA.
5. Take default on the remaining steps, and after domain creation the "Run Database Scripts" dialog box shouldn't appear, and the domain should start properly.I'm curious though as what would one do if instead of PointBase DB, we use MS SQL 2000,
for all the relevant databases in an Integration domain? Thanks.
---Nam -
Weblogic Integration 9.2 - Domain Configuration SQLAuthenticator
hi
<p>
After downloading, the new vesrion, I started to use the Configuration Wizard to set up a Test Domain.
<p>
At the completion of the configuration, the following message is presented:
<p>
"This domain is configured to use the SQL authenticator security provider. You must load database tables in the "Run Database Scripts" panel or load the tables manually after completing the wizard using the SQL file located at ..... /security/SQLAuthenticator.sql"
<p>
1: This is something new as far as I can tell. At least I've never encountered it and I have installed earler versions of 9.2, ALSB recently
<p>
2: when setting up a new domain, neither the server nor pointbase are running. Hence the scripts cant be run from withiin the Config Wizard.
<p>
3: Cant start the Admin server for the new domain because the tables are not set up
<p>
4: How do I run the .sql script manually? I'm assuming the PB Console but I dont actually know the Pointbase Datbase name that I should connect to for this purpose
<p>
5: I can't find any discussion of this in the release notes, upgrade notes etc.
<p>
So I'm stuck. This seems a pretty strange way to do things. Any advise would be appreciated.
<p>
Regards
<p>
Jim NicolsonT C wrote:
I have also run into the "Run Database Scripts" dialog box after creation of a domain. When I started the domain I got the following error:
<[Security:090737]An exception occured while getting connection to validate the configuration settings
va.sql.SQLException: [Security:090735]The DBMS connection was not usable
I have BEA 9.2 Platform running on Windows 2000 Professional Service pack 3.
Incidentally, I started pointbase manually (startPointBase.cmd), started PointBase Console (startPointBaseConsole.cmd) in order to execute the SQLAuthenticator.sql script. This all failed because this SQL script refers to tables GROUPS and USERS, which did not exist in my PointBase schema.
What worked for me was:
1. Create a new domain, and only select Workshop for WebLogic, WebLogic Portal, and WebLogic Integration options.
2. Select YES to Customize Environment and Services Settings tab.
3. Take defaults until the Run Database Scripts dialog box.
4. On the Run Database Scripts dialog box, run the scripts for p13nDatasource and cgDataSource-nonXA.
5. Take default on the remaining steps, and after domain creation the "Run Database Scripts" dialog box shouldn't appear, and the domain should start properly.I'm curious though as what would one do if instead of PointBase DB, we use MS SQL 2000,
for all the relevant databases in an Integration domain? Thanks.
---Nam -
Problem on starting weblogic integration 2.1
I would like to ask you for advise/information on the start-up of the
weblogic integration 2.1.
I have tried to setup the weblogic integration 2.1 (sp1) at home, but
without any success yet.
There was nothing helpful that I can found in the BEA knowledge base.
My weblogic server 6.1 (sp2) starts up alone normally and working fine, and
I have followed
all the steps in the installation document, including create and setup the
database.
I have also executed the setenv.cmd and make sure the domain in use is
"wlidomain".
When I try to start up the weblogic integration 2.1, it give me the
following exception.
C:\bea\wlintegration2.1\config\wlidomain>startWeblogic.cmd
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ArrayIndexOutOfBoundsException
at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
at com.bea.utils.misc.Process.validate(Process.java:1231)
at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:286)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance, and looking forward for your reply soon.
Best Regards,
Matthew HoHi.
Try posting this on either weblogic.integration.interest or
weblogic.integration.developer.
Thanks,
Michael
Matthew Ho wrote:
I would like to ask you for advise/information on the start-up of the
weblogic integration 2.1.
I have tried to setup the weblogic integration 2.1 (sp1) at home, but
without any success yet.
There was nothing helpful that I can found in the BEA knowledge base.
My weblogic server 6.1 (sp2) starts up alone normally and working fine, and
I have followed
all the steps in the installation document, including create and setup the
database.
I have also executed the setenv.cmd and make sure the domain in use is
"wlidomain".
When I try to start up the weblogic integration 2.1, it give me the
following exception.
C:\bea\wlintegration2.1\config\wlidomain>startWeblogic.cmd
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ArrayIndexOutOfBoundsException
at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
at com.bea.utils.misc.Process.validate(Process.java:1231)
at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:286)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance, and looking forward for your reply soon.
Best Regards,
Matthew Ho--
Michael Young
Developer Relations Engineer
BEA Support -
Cannot run WebLogic Integration Samples from QuickStart
I have installed the full WebLogic platform on an Intel box running Red Hat Linux
8.0. From QuickStart I am unable to run the WebLogic Integration Samples. Everything
else seems to work as expected.
The error message that results when attempting to run the Integration samples
is as follows:
RunSamples execution failed: /usr/local/bea/weblogic700/samples/integration/samples/lib/RunSamples.xml:106:
Cannot execute switchdb pointbaseDear Micha,
Did you maintain the host file in Drivers\etc file:
hope this will solve the problem
If you did not add them plz add the hosts as follows:
102.54.94.97 rhino.acme.com # source server
38.25.63.10 x.acme.com # x client host
(your PI server IP) server Id name
And also check your Java web start version.
download the correct version for sun website.
Best Regards
Praveen K Kurni -
Server1 canot start on weblogic integration cluster
I can not start server1 on weblogic integration cluster, out and logs are:
<> <1345403377689> <BEA-000000> <Error in startup class com.bea.wli.management.configfile.ConfigFileManager Method: initialize:
java.lang.AssertionError: MBeanHome lookup failedjavax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management';
remaining name 'adminhome'
at weblogic.management.Admin.lookupMBeanHome(Admin.java:245)
at weblogic.management.Admin.getAdminMBeanHome(Admin.java:260)
at com.bea.wli.management.MBeanHelper.getMBeanHome(MBeanHelper.java:161)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:100)
at com.bea.wli.management.configfile.ManagedRepAgent.<init>(ManagedRepAgent.java:83)
at com.bea.wli.management.configfile.ManagedConfigFileManager.<init>(ManagedConfigFileManager.java:53)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:101)
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 com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:287)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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: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.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Aug 19, 2012 4:09:37 PM BRT> <Critical> <WebLogicServer> <adriana> <server1> <Main Thread> <<WLS Kernel>> <> <> <1345403377696> <BEA-000362> <Server failed. Reason
There are 1 nested errors:
java.lang.AssertionError: MBeanHome lookup failedjavax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management';
remaining name 'adminhome'
at weblogic.management.Admin.lookupMBeanHome(Admin.java:245)
at weblogic.management.Admin.getAdminMBeanHome(Admin.java:260)
at com.bea.wli.management.MBeanHelper.getMBeanHome(MBeanHelper.java:161)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:100)
at com.bea.wli.management.configfile.ManagedRepAgent.<init>(ManagedRepAgent.java:83)
at com.bea.wli.management.configfile.ManagedConfigFileManager.<init>(ManagedConfigFileManager.java:53)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:101)
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 com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:287)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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: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.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)Hi Alex,
That's weird, I have WLI installed here in some of the servers, but there is no ConfigFileManager startup class...
Go to the config.xml file and comment out all startup and shutdown classes and see if that helps to start the server at least... You may have to reinstall WLI though...
Hope this helps...
Cheers,
Vlad -
Installation hangs at 72% during Weblogic server 9.2 installation
I had already Weblogic portal server in my machine working fine. 3 days back when I opened workshop, it said "Could not create Java Virtual Machine" and was not starting. After that I reduced xms and xmx values in workshop.ini file and it worked but it gave other problems like outofmemory. So, I uninstalled that.
And When I tried to reinstall the Weblogic portal 9.2, installation went till 72% and when it turned to "Creating Sample Domains..." it got hang. I couldn't install it at all. Can someone please explain why it happened and how to resolve it? First of all I could not understand why suddenly it said "Could not create Java Virtual Machine"???????
I have Windows Xp Service pack 2 with 3 GB of RAM memory and 7 GB free space in C drive.Dear Senthil,
It seems your RAM is getting utilized by some other processes on your machine , Check all of them as you have enough RAM required by WLS. Also for next installation , delete all the files created by earlier installation .
Also importantly unset the environment variables got set by earlier WLS installation. -
Homesite5.0 fails installation in vista
homesite5.0 fails installation right away after giving me
error:
in function sdcomponenttree unable to create dialog
then gives me a blank error box
then a series of blank abort/retry/ignore boxes throughout
installation
creates start menu dir, but no shortcut
does not copy files, does not create program files dir.
tried running as administrator, tried setting setup file to
xp compatibility to no avail.
anyone have experience with this problem?Hi Bill, yes, I can do that. Created one several levels deep.
I assume you mean HS is running on Vista. It's not clear if you're
problem is in creating that directory on RDS remote host (from a HS
client running Vista) or specifically in also creating the
directory on an RDS remote host (or localhost) running Vista. I was
able to create a directory several levels deep on both a remote
machine (not running Vista) and my localhost running Vista, both
via RDS.
I'll add, FWIW, that I'm running HomeSite+ 5.5 (not HomeSite
5.0). If you (or others) really are still on 5.0, there's at least
a free update to HS 5.2 (
http://www.adobe.com/cfusion/resourcecenter/resourcecenter.cfm?pagename=hs%5F52%5Fupdater& loc=en%5Fus&)
To update to HS 5.5, it would cost a HS 5.0 customer US$29.
More at
http://www.adobe.com/products/homesite/productinfo/upgrade/
That said, no release of HS specifically lists Vista as
supported (see the requirements page, which lists Win2k3 as tha
latest OS specifically supported):
http://www.adobe.com/products/homesite/productinfo/systemreqs/
I'll point out as well that if one has Dreamweaver 8, that
includes HomeSite+ 5.5 free on the CD (you use the DW license to
register it).
If anyone would ask about the difference between HomeSite and
HomeSite+, I'd point you to a blog entry I did (one of many, by
myself and others over the years):
http://carehart.org/blog/client/index.cfm/2007/10/23/homesite_homesiteplus_and_adobe_eclip se_ext
Hope that's helpful.
Maybe you are looking for
-
How can I change my icloud account without knowing the old password
How can I change my icloud account on my phone when I don't know the old password and I'm on a shared plan
-
Hi, Message no. CT608 During creation of breakdown order for equipment the screen gives error that scheduling parameters are to be entered for maintenance order.But i am not understanding why we should enter scheduling parameters when we are not crea
-
I finally got things working but for one small problem: Why does it take so long for each plug-in to load so that I can begin working on an image with it? Is this just a part of the program?
-
871 802.1x with vlan assignment aka dynamic vlan
you can do vlan assignment on 871W wireless using the local radius server but unfort only LEAP which is N.G. I have been pounding on wired 802.1x PEAP (which works) trying to get vlan re-assignment. Have tried with IAS which I am using to do vlan rea
-
Interpret items in watch folder
Is is possible to interpret the footage of items in a watch folder - for example, I have a lot of Avid DNxHD120 exported at 1080i but I'd like the output .mp4 files to encode properly to progressive. If I don't interpret the footage manually as upper