Weblogic Integration WLW Message Queue Problem
I am using BEA Weblogic Integration (BEA WLI). While testing processes, I get the following error on Weblogic Server Console:
<Feb 27, 2006 10:56:55 AM CET> <Warning> <WLW> <000000>
A message was unable to be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure event
Please can you suggest what can be the problem.
The bridge does not do anything to the properties on the messages. It just sends the messages that it received from the WLS JMS queue to MQSeries queue.
Have you tried to receive directly from the WLS JMS queue and see if the receiver can retrieve the String property?
Dongbo
Similar Messages
-
A message was unable to be delivered from a WLW Message Queue
when my application passing the some message to other components through the WLI, and i got the following exception.
<Oct 5, 2007 1:41:29 AM EDT> <Info> <EJB> <BEA-010213> <Message-Driven EJB: AsyncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA1-00B19848F1EF94ECBDBF(19675354),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_cgJMSStore_auto_1]=(ServerResourceInfo[JMS_cgJMSStore_auto_1]=(state=rolledback,assigned=WOSServer1),xar=JMS_cgJMSStore_auto_1),SCInfo[WOSDomain+WOSServer1]=(state=rolledback),properties=({}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@12aeef2]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=Server1+91.11.81.30:7111+Domain+t3+, XAResources={JMS_cgJMSStore_auto_1, weblogic, Connection Pool},NonXAResources={})],CoordinatorURL=Server1+91.11.81.30:7111+Domain+t3+).>
<Oct 5, 2007 1:41:29 AM EDT> <Warning> <WLW> <000000> <A message was unable to be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure event>.
please provide me any suggestions on this problem.And I believe this would be better suited for the EJB forum since it doesn't seem to have anything to do with JSP/ JSTL: http://forum.java.sun.com/forum.jspa?forumID=13
People on the forum help others voluntarily, it's not their job.
Help them help you.
Learn how to ask questions first: http://faq.javaranch.com/java/HowToAskQuestionsOnJavaRanch
(Yes I know it's on JavaRanch but I think it applies everywhere)
---------------------------------------------------------------- -
JES5 on HPUX C API Message Queue problem
OK. I know there's not too many of you out there, but I've been trying to compile a simple "C" helloworld pub/sub application using GCC. The examples shows using 'aCC' instead of 'gcc' to compile on HPUX. I'm able to compile using gcc, but the application core dumps.
Is the Message Queue, C-API & library compatable with applications compiled with gcc on the HPUX platform? Or will i have to use HP's Ascii C Compiler to get it to work.
gcc build options:
g++ -x c -fPIC -DHPUX11 -D_REENTRANT -I/opt/sun/mq/include -o Producer -L/opt/sun/mq/lib -L/opt/sun/private/lib -lnss3 -lmqcrt -Wl,+b,/opt/sun/private/lib Producer.c
Error during execution:
/usr/lib/dld.sl: Unresolved symbol: __shlinit (code) from /opt/sun/mq/lib/libmqcrt.sl
Abort(coredump)
Thanks
Message was edited by:
weinhardAfter switching to HP's ANSI C compiler i get the exact same error message.
Any ideas as to what the permissions should be on the symbolic link to the real shared library. The installed permisstion/owners are:
lrwxr-xr-x 1 bin bin 29 Sep 12 00:45 libmqcrt.sl -> /opt/sun/mq/lib/libmqcrt.sl.1 -
Weblogic Integration : xml message for event node in a workflow
Hello,
I have the following queries for weblogic 7.0 BPM workflows with event nodes:
1) How does weblogic server choose that an xml message should be delivered to
what all workflow instances, as the xml event does not carry any information regarding
the workflow instance or event node?
2) When an XML message is received, but there are no eligible consumers (workflow
instances) then what happens to the message, is it discarded?
3) Suppose an xml message comes for an event node even before that event before
has been reached in the workflow instance, ie, the event node has not been activated
yet. Is the message persisted to be delivered for processing when the event node
gets activated or is it discarded?
Please reply at an earliest.
Thanks,
ParulHi,
Based on your description what I felt is you are making use of a wait step in which you have choose to wait till BUS2078 event CREATED is occured ... right.. Now can you please clear me that where and how this event will triggered.
or is it some thign like you are making use of event creator step and in this case, When ever you are making use of the eventcreator step and a BOR object inside it make sure that specific BOR object is already instatitaed in the workflow container , if it is instantiated then only it will try to identify the instance or the BOR and it will try to rasie the event.
Regards
Pavan -
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,
LinusI 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 -
Weblogic Integration 2.1 problem
<b>I have installed Oracle 9.X then installed Weblogic 6.1 and then installed Weblogic Integration 2.1
after instalation i have started Weblogic server by clicking wlintegration2.1/config/bpmDomain/startWeblogic.cmd
Then i am getting this problem</b>
java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX
DataSource']
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundExcept
ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres
olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX
DataSource']
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.getConfiguredPlugins(
PluginManagerCfgImpl.java:749)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.initializePlugins(Plu
ginManagerCfgImpl.java:873)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(PluginManagerCfg
Impl.java:80)
at com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(Pl
uginManagerCfgBean_gebmxi_EOImpl.java:1300)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListe
nerBean.java:153)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Oct 31, 2006 4:49:49 PM IST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "myserver" for domain "bpmdomain" running in Production Mode>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource.
Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name ''
<<no stack trace available>>
<b>Please resolve this ASAP</b>.I'm having this issue as well. Can you tell me how you fixed the problem???
Thanks -
Can you talk to WebLogic Message Queues with C/C++
Just curious, can you talk to message queues in WebLogic with C/C++, or do you jave
to use the JMS API to get to it?
We have some existing C/C++ code we need to communicate with and we are considering
using message queues to do it. We have tried it with MQSeries and it works fine,
but could we do the same thing with WebLogic. We already have WebLogic in production
and would like to avoid having to also buy MQSeries just to integrate to the C/C++
code and messaging is a lot easier than dealing with JNI.
Any advise would be greatly appreciated!!!
Hi Chuck,
Here are some options:
www.codemesh.com provides a C++ JMS wrapper (via JNI), one customer has instead
recommended "Jace" http://sourceforge.net/projects/jace/
Alternatively use RMI over IIOP to invoke an EJB that in turn calls JMS (WebLogic
understands IIOP).
Alternatively use HTTP/WebServices/SOAP.
Personally, I think RMI/IIOP is an interesting option, post to the rmi-iiop newsgroup.
Tom
Chuck wrote:
> Just curious, can you talk to message queues in WebLogic with C/C++, or do you jave
> to use the JMS API to get to it?
>
> We have some existing C/C++ code we need to communicate with and we are considering
> using message queues to do it. We have tried it with MQSeries and it works fine,
> but could we do the same thing with WebLogic. We already have WebLogic in production
> and would like to avoid having to also buy MQSeries just to integrate to the C/C++
> code and messaging is a lot easier than dealing with JNI.
>
> Any advise would be greatly appreciated!!!
-
Problem with GlassFish and Sun Java System Message Queue
Hi,
I used application server PE.8 and I upgraded to Sun Java System Application Server Platform Edition 9.0 Update 1 Patch 1, and I changed all my CLASSPATH and everything. My system is working fine, but the Sun Java System Message Queue that I used before is still showing the queues and physical queues of the previous application server, not the new one. Do you know if there is way to change that and link it to the new version?
thanksUse an ESB like ServiceMix to bridge JMS providers
http://servicemix.org/
Or write your own MessageListener to consume from one JMS and publish on another one. Be careful with queues to avoid loosing the ordering - so you probably want to use a single MessageListener per subscription/queue - or to take advantage of Tibco's exclusive queues to ensure ordering is preserved. If ordering doesn't matter then don't worry too much about it and maybe have a pool of consumers to improve throughput
James
http://logicblaze.com/ -
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 -
Re: Constant Message Redelivery Problem
You can get redelivery for other reasons as well. Redelivery occurs if the message is
participating in a transaction, and the transaction fails for any reason.
For example, if the MDB in turn calls an EJB which in
turn calls JDBC then the tx becomes two-phase. If the JDBC call fails then the tx
will roll back. Or if the tx times-out: the default tx timeout is 30 seconds, so if
the MDB takes longer than 30 seconds then the tx will roll-back and message the will
get redelivered.
Even if the tx succeeds, in some cases you may have error states that re-enqueue the
received message but let the transaction commit (WLI, BEA's integration product, can do
this).
This looks like the redelivery of a failed message, but is actually the delivery of a new
version.
Duplicates occur if a Queue MDB's descriptor actually points at a topic destination.
Check for this one by comparing the JNDI name in config.xml against the
descriptor destination type field...
Tom
sunshine wrote:
> I encountered the same problem of repeat message delivery. In our situation, we are
> using JMS JDBC Store and when the database goes down and comes back up, the MDB starts
> processing messages but the messages keep recycling in the JMS Store.
>
> The MDB code tried catching all possible exceptions like RuntimeException and Exception.
> None of these exceptions are logged. When we re-start the WL managed servers, those
> messages in the JMS Store were flushed off.
>
> Any idea what caused the repeat message redelivery?? Thanks.
>
> Tom Barnes <[email protected]> wrote:
> >Your MDB may be throwing a RuntimeException, which forces message
> >redelivery. Put a try/catch/Throwable in the outermost scope of your
> >onMessage() code to see if this is case.
> >
> >Note that in 6.1 and up you can configure redelivery delays, max redelivery
> >counts and error destinations to alleviate this problem...
> >
> >Tom
> >
> >Toad wrote:
> >
> >> I have a message-driven bean listening on a message queue and everything
> >> appears to work the first time the message is sent. The message is processed
> >> and the OnMessage method returns without incident. There are no errors
> >and
> >> no exceptions are thrown by the JMS client or in the MDB itself. PROBLEM:
> >> Message continually redelivered pegging the CPU at 100%. Inspection of
> >the
> >> JMSSTORE and JMSSTATE reveals messages still queued. Any ideas?
> >
And make sure that your MDB is not throwing Errors or RuntimeExceptions,
as these don't necessarily get logged, but they cause rollbacks.
Put a "try {} catch (RuntimeException re)
{ log; throw re; } catch (Error er) { log; throw er; }"
around all the code within the MDB's "onMessage()" callback
to see if this is happening.
Manikyala Peddi wrote:
> Hi,
>
> I have a MDB which is calling an EJB. The redelivery override period was set at 60 sec.
>
> Before completing the first message the same message is redelivered.The processing time in onMessage in MDB takes more than the Redelivery Override Period. Is there a way to prevent the delivery of the duplicate message before completing the first message.Iam using Weblogic 7.1
>
> Thanks
>
> Manikyala
-
Weblogic Integration 10r3 error in msg-header-2_0.xml
Hello,
I am trying to go through te WLI workshops, but cannot publish a WLI process.
The Tutorial_Process_Application RequestQoute.java has the following error in the msg-header-2_0.xml:
Severity and Description Path Resource Location Creation Time Id
Referenced file contains errors (http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd). For more information, right click on the message and select "Show Details..." Tutorial_Process_Application_Utility/schemas/system msg-header-2_0.xsd line 1 1257804610777 410
A new WLI project from scratch gives te same error, it is as if the msg-header-2_0.xml is not correctly generated when the WLI process is created.Aha! problem solved :)
The tutorial states : 'Select the Add WebLogic Integration System and Control Schemas to Utility Project check box to add the system schemas to the Schemas folder under the Utility project.'
If you do that it does not work, and i get the errors I discribed in the post, howerver if ypu leave it blanked out, the process can be published, without error or warnings.
As I am new to WLI (use to work with Oracle Bpel) I have no idea about the importance of adding the Integration system and control schemas to the utility project.
However as my goal is to work through the workshops, I wil worry about it later.
Edited by: DaveVQ on 14-nov-2009 5:39 -
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 -
OSB 10.3 JMS queue problem: JMSCorrelationID is null
Hi everybody,
I am new to OSB/ALSB, and need some help regarding JMS message handling. I am trying to put some input data into a JMS queue( say, reqQueue) and to get the response from another JMS queue(say resQueue). My architecture is:
OSB proxy service->OSB business service->JMS queue(reqQueue)->BPEL process(through JMS adapter) ->JMS queue(resQueue)->OSB business service->OSB proxy service.
I have used JMSCorrelationID for response correlation. but my problem is that when I am trying to test the service from proxy service, I am getting the JMSCorrelationId as null in BPEL process as well as in the weblogic server JMS log, and as I am getting the CorrelationId as null, I am unable to correlate the response, so I am not getting any response.
This is urgent, please help me as soon as possible as possible.
Thanks in advance.
JoySovled it..
OSB 10.3 JMS queue problem: JMSCorrelationID is null -
Weblogic Integration Sample is available for download from developer site
Hi, All,
The Weblogic Integration 2.0 Sample is available for download from the
developer site:
http://developer.bea.com/ftp_bin/download/code/wliSample_1.zip
This sample shows how to develop a standard based integration solution
within and across enterprises using the key functionalities of the WebLogic
Integration 2.0, including Business Process Management (BPM), Enterprise
Information System (EIS) connectivity, inter-enterprise collaboration
(B2Bi), and XML/non-XML data transformation.
Chunbo Huang
BEA SystemIt shoud not took 3 hours. Normally, you expect wait for 1 -2 minutes.
For your case, I suggest to
(1)run the cleanWF.cmd script then shutdown the server
(2)restart the server
(3) run cleanWF again
(4) run the sample.
let me know if you still have problems
Chunbo
"Chris Stead" <[email protected]> wrote in message
news:[email protected]..
Chunbo/Henry,
While running the WLI sample, I have been waiting for a QPA Reponse frommy
suppliers for about three hours, is this expected behavior? I havechecked the
weblogic.log file and there are no exceptions. I seem to be stuck on the
"Check QPA Reponse" screen. This was addressed briefly in the user guide,
however, it didn't say how long you should wait. Please advise, thanks.
Cheers,
Chris
Chunbo Huang wrote:
Hi, All,
The Weblogic Integration 2.0 Sample is available for download from the
developer site:
http://developer.bea.com/ftp_bin/download/code/wliSample_1.zip
This sample shows how to develop a standard based integration solution
within and across enterprises using the key functionalities of the
WebLogic
Integration 2.0, including Business Process Management (BPM),Enterprise
Information System (EIS) connectivity, inter-enterprise collaboration
(B2Bi), and XML/non-XML data transformation.
Chunbo Huang
BEA System -
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.
Maybe you are looking for
-
How to create a new company code and how to assign it to billing units?
i am working on roll out project.....please help me in creating a new company code....
-
6.0.3 Error During Disc Initialization for both DVD+R and Disc Image - Help
I've been a mac user for a few years now, but I just bought a new MacBook, and my first superdrive! I'm all excited to test out the new hardware along with iDVD. I've made a rather simple DVD setup and the first time through it was encoding for about
-
TS - Cannot install specific product from Autodesk suite
Hi, the scenario is the following: SCCM 2012 R2. All in one server. Windows 2012 R2. Windows 7 Pro x64 (clients) After sccm client installation step, the task sequence successfully install another autodesk products (autocad, inventor, revit) but fail
-
Word import/linking - index keywords and cross-ref conversion options
Hi all, there are two options for linking/importing Word documents that seem to have no function. Maybe somebody can clarify what these are used for? * First, the option "Add index keywords to topics" in the link properties is always greyed out, even
-
Hi, I need to update the receipts DFF's using API.I checked with Ar_receipt_api_pub,but there is no code for updating receipt.Is there any API to do this, could anyone please help me.. Thanks in Advance.