Macromedia live cycle 7.2 매뉴얼
Adobe LiveCycle
Manually Deploying to JBoss
Installing and Configuring LiveCycle for JBoss
Applying the connection pool patch for Watched Folder 65
8. (LiveCycle PDF Generator for PostScript) Copy the pdfg-ps-all.ear file from the
[LiveCycle root]/configurationManager/export directory to the [appserver root]/server/all/deploy
directory.
directory.
9. Restart JBoss to ensure that the applications start up.
Note:
When you start JBoss, you may see several error messages in the JBoss server log file. These
messages occur if you have not yet initialized the database.
messages occur if you have not yet initialized the database.
Applying the connection pool patch for Watched Folder
When Watched Folder is under load for a certain amount of time (in hours), JBoss 3.2.5 throws an
exception because all of the database connections in the connection pool are busy. This is a known issue
in JBoss 3.2.5. The connection pool patch modifies the jboss-jca.sar file.
exception because all of the database connections in the connection pool are busy. This is a known issue
in JBoss 3.2.5. The connection pool patch modifies the jboss-jca.sar file.
Apply this patch when using Watched Folder in a production environment or when testing
Watched Folder under load in a test environment. (The patch is not required for using Watched Folder for
basic demonstration or test purposes.)
Watched Folder under load in a test environment. (The patch is not required for using Watched Folder for
basic demonstration or test purposes.)
➤
To apply the connection pool patch to JBoss 3.2.5:
1. Stop the JBoss service.
2. Replace the jboss-jca.sar file in the [appserver root]\server\all\deploy directory with the jboss.-jca.sar file
in the [LiveCycle root]\configurationManager\deploy\jboss\ directory.
3. Restart the JBoss service.
Viewing log files
Events, such as run-time or startup errors, are recorded to the application server log files. If you have any
problems deploying to the application server, you can use the log files to help you find the problem. You
can open the log files using any text editor.
problems deploying to the application server, you can use the log files to help you find the problem. You
can open the log files using any text editor.
The following log files are located in the [appserver root]/server/all/log directory:
●
boot.log
●
server.log.[yyyy-mm-dd]
●
server.log
Next step
You must now initialize the database using Configuration Manager.(See