之前我们就提到，这通常是由不兼容的Jar文件或其他库以及类加载问题所引起的。
We mentioned earlier that usually this is caused by incompatible Jar files or other library and class loading issues.
本发明解决目前用户数据加载速度慢及故障宕机而导致的用户数据重新加载问题。
The invention solves the problems that the user data has slow loading speed and the user data needs to be loaded again by the fault at present.
此异常发生在一个非常具体的方法调用，在同一个类的方法组装已经叫，所以我认为它排除装配加载问题。
This exception happen in a very specific method call, after methods of the same class as assembly are already called, so I think it rules out assembly loading issues.
针对矿修车间的采煤机截割部的加载问题，研制开发面向维修的采煤机截割部加载试验台，对维修后的采煤机截割部进行加载试验。
Aim to the problem of cutting part with shearer at the mechanical repair workshop, the loading test bed for shearer cutting part undergoing maintenance is manufactured.
所以，剩下的问题就是如何获取这些测试定义、如何将它们加载到DOH的UI 中以及如何执行它们。
So, the question that remains is how do you take these test definitions, load them into the DOH's UI, and execute them.
毫无疑问，如果这个链条中的任何一个插件不能成功加载，那么依赖它的插件就可能会出现问题。
No doubt, then, that if any plug-in in this chain fails to load successfully, the dependent plug-ins may have problems.
这样做的最大问题是新型的处理器很可能加载此DTDURL，而这可能是一种不必要的网络操作。
The biggest problem with this was that a naive processor is likely to load that DTD URL, which might be an unwanted network operation.
这样做，一旦加载了错误的类或错误版本的类，就会出问题。
It will cause problems when you load the wrong class or the wrong version of a class.
因为每个匿名类都有一个唯一的名称，因此在加载该类是不会有问题的，而这样做的结果是，应用被实时动态地更新了。
As each anonymous class has a unique name there are no issues loading it and as a result the application is updated on-the-fly.
动态类加载是动态jit编译器面临的一个挑战，也是AOT编译的一个更重要的问题。
Dynamic class loading, which is a challenge for the dynamic JIT compiler, is an even more significant issue for AOT compilation.
类加载被沙箱化到每个捆绑包，因此日志记录框架这样的依赖项在捆绑包之间即使不同也不会导致问题。
Class loading is sandboxed to each bundle, so dependencies such as logging frameworks can be different between bundles without causing problems.
不过，问题是加载证书的函数并没有请求使用加密证书的密码。
The trouble, though, is that the functions that load the certificates do not ask for a password for encrypted certificates.
通过下面的示例代码来了解一下延迟加载所面对的问题及解决办法。
Let us take a sample code to see the issues faced using lazy loading and a solution to overcome it.
不幸的是，有问题的插件很可能并不属于成功加载的插件。
Unfortunately, your problematic plug-in probably does not fall into this category of plug-ins successfully loaded.
延迟抓取的另一个问题就是在获取到请求的数据前要一直打开数据库连接，否则应用就会抛出一个延迟加载异常。
Another issue with lazy fetching is that the database connection has to be retained until all the required data is fetched else the application will throw a lazy loading exception.
第一个问题是对于数据何时被加载没有任何提示。
The first problem is that there's no indication of when the data has been loaded.
问题是，您忽略了延迟加载内容（或太过复杂而不能考虑这个选项），特别在构建中包括所有小部件的情况下。
The problem is that you negate (or make it extremely complicated to) lazy load content, especially if you include all your widgets as part of a build.
这些影响可能小到只是影响某个页面的加载或表单保存，也可能是产生难以检测的问题，或者产生只在特定条件下才会出现的错误。
The effects may be as simple as a page not loading or a form not saving, or could also be something hard to detect or only shows up under certain circumstances.
JPA允许通过注释来“懒散地”加载属性，但正如我们在后面看到的，当考虑到实体是一个POJO时，此方法自身也有问题。
JPA allows for "lazily" loading the properties through annotation, but as we will see in a later point, this approach creates its own problems when coupled with thinking that the entity is a POJO.
我并不会尝试解决所有的核心问题，例如“加载浏览器url”或者“告诉我什么时候我的应用能够运行”。
I'm not trying to solve all the nitty-gritty problems across devices like "launch a browser URL" or "tell me when my app code can start".
在多个查询语句的执行过程中需要保持数据库连接，否则会抛出一个延迟加载异常，这将导致数据出现问题。
Database connection needs to be maintained for the duration of the multiple query cycle else a lazy loading exception is thrown, resulting in inadequate use of resources.
如果我们将所有的设备驱动程序从BIOS 中删除，显然有很多问题都需要考虑：BIOS是否没有加载所有的设备驱动程序？它怎样读取内核？
There's an obvious concern that arises if we eliminate all of the device drivers from the BIOS: if the BIOS isn't loading all of these device drivers, how can it read the kernel?
要解决这些问题，需要另外一种不同的方法加载页面及其上的组件。
To get round many of these problems requires a different approach to the way pages and the components on those pages were loaded.
这种方法的问题在于你失去了只加载部分框架内容的能力，并增加了维护的难度。
The problem here is that you lose the ability to include only certain parts of the framework, and you also make maintenance more difficult.
问题是，加入的所有空格、分行符、注释都增加了脚本文件大小和应用程序的加载时间。
The problem is, all of the whitespace, line breaks, and comments that you add to your code increase the file size of the script and the load time of your application.
由于can notmount rootfs错误主要是由设备顺序造成的，更改设备顺序或者更改驱动器加载顺序将解决此问题。
Since the cannot mount rootfs error is mostly caused by device order, changing the device order or changing the driver loading sequence will solve this problem.
为了确定页面加载缓慢的原因，特别是在问题零星出现的时候，在生成的HTML源代码中添加调试计时信息可能非常有用。
To identify the cause of slowly loading pages, especially when the problem is sporadic, it can be useful to add debug timing information into the generated HTML source. These timings can be for
应用程序试图通过调用带有MAP_ FIXED标志的mmap从绝对地址加载代码时会产生一个相关问题。
A related problem is caused by applications that try to load code at an absolute address by calling mmap with the flag MAP_FIXED.
下列IBM 技术札记（technote）谈到了加载一个表时运行RUNSTATS可能碰到的问题。
The following IBM technote talks about a possible problem that may be encountered with RUNSTATS when loading a table.
这些问题可能发生在加载twitter.com页面和Twitter客户端时。
There may be intermittent issues loading twitter.com and Twitter clients.
应用推荐