• DAnalyzer 1.2发布啦 -- Weblogic与Directory协议分析工具

  • SQLView -- 可视化的Weblogic JDBC DEBUG

/Articles

Transaction Timeout in Agile + Weblogic

We may see different transaction timeout error in Agile (It also happens to other applications). There are two places where control the Timeout setting, JTA, EJB tier and Loadbalancer/Proxy. I will demonstrate three cases to show how to identify them. Though most of the timeout issues are caused by...

Agile File Server impacted by TCP Compression Solution

Usually, Agile JavaClient is only used internally. Here "internally" I especially means the LAN in same physical location. I do not suggest it to be "externally" used across WAN or VPN. That is because JavaClient is a fat client, each EJB invockation involves too much redundant data in TCP...

Develop PHP HTTP Destination for Agile PLM ACS

I seldom see customer use HTTP Destination for Agile ACS because of its code difficulty. But someone ever asked this question about how to code PHP program as the HTTP destination to process ACS data from Agile PLM. In our Agile PLM ACS User Guide, there is only one sample HTTP head data for...

Agile JavaClient and Java Web Start

JavaClient uses Java Web Start technology to launch all required jar files and resources into local cache to deploy with online and offline mode. We will discuss how JavaClient is loaded from remote Application Server. Detect Java Web Start Usually we access JavaClient from the entrance...

Poorer performance of IQuery in 9.3.0.3 than 9.3.0.1

Recently we got several customers' report that the IQuery API in client SDK program has poorer performance in Agile 9.3.0.3 than 9.3.0.1. If to monitor SDK client program's memory heap usage we will see much more heap is used in 9.3.0.3 and Wireshark monitor shows more data packages are received...

Checksum in Agile File Server

We will discuss the concept of checksum in Agile PLM and related technology. If enabled Checksum Calculation in Agile PLM, we may see below error when do CheckOut/CheckIn file attachment. This scenario means the original physical file is modified by external program beyond Agile. There are quite...

Background execution of IQuery API in Agile SDK

I have been asked by customers and partners about one same puzzle that why IQuery.execute() runs extremely fast, while the first time execution of Iterator.hasNext() runs very slow。To answer and summarize the background technology of IQuery, let's analyze it detailedly. Below is a very typical...

线程分析-线程池溢出

Java中的线程池溢出,是个比较难诊断的问题。它的成因是多个任务(比如HTTP请求)等待执行,因为每个thread在一个时间点上只能执行一个task,如果线程池最多可以容纳20个线程,涌进来30个任务,那么只有20个任务才能得到执行,剩下的10个必须等待池中出现闲置的线程。如果有一些执行的任务很耗时,后面的任务将长时间得不到线程资源供执行,线程池溢出的问题就会发生。 很多web服务器都提供了线程池的技术,可以动态扩展,但都有一定的限额。下面的代码演示线程池溢出的问题,代码相对复杂,但能很好地解释这个现象。 代码演示...

线程分析-资源竞争

Java线程问题中最为常见的成因是资源竞争,它导致的后果是服务器停止响应,或者CPU过高使用。资源竞争非常好理解,就是一个或者多个线程等待某个资源,而这个资源又被另一个线程所占有并长时间不能释放。对于这种情形,Thread Dump中的“waiting for monitor entry”就非常重要。 代码演示...

线程分析-DeadLock

Java中谈线程问题必谈死锁,这种现象很奇怪。因为死锁的发生还是比较少见的,它是经典的线程问题但绝对不是常见的。它一般不会引起CPU使用过高,相反地,它会使得服务器停止对客户请求的响应。死锁的问题很容易就能从Thread Dump中识别出来。 这里有一点需要明确的是:死锁和CPU过高使用没有必然联系。但是网络上经常讲CPU过高和Java线程就归纳到死锁上来。这是不正确的。线程问题有很多种类,死锁只是其中一种很少见的情况。 下面通过具体的代码来演示死锁的产生,并通过Thread...

1 2 3 4 5 6 7 8 9 10 11