IBM E02HRLL-G Administration Guide - Page 174

Disabling JIT in a WebSphere Application Server when WebSphere Partner Gateway produces a javacore

Page 174 highlights

REPROCESSOR_HOME=Document Manager installation root JAVA_HOME=$REPROCESSOR_HOME/java LOG_REPROCESSOR_CLASSES=$REPROCESSOR_HOME/classes 2. Run the utility from the command line: ./reprocessDbLoggingErrors.sh or reprocessDBLoggingErrors.bat Disabling JIT in a WebSphere Application Server when WebSphere Partner Gateway produces a javacore About this task When WebSphere Partner Gateway components (Receiver, Document Manager, or Console) end abruptly and produce a javacore, it is typically because of a problem with the Java JIT compiler. If this behavior occurs, disable JIT from the WebSphere Application Server Admin Console. To disable JIT from WebSphere Application Server: 1. Logon to WebSphere Application Server Admin console. 2. Under Servers, click Servers and select the WebSphere Partner Gateway Server. 3. On the configuration page, select Java and Process Management > Process Definition. 4. In Additional Properties select Java Virtual Machine. 5. Select the Disable JIT check box. Defining a custom transport type When defining a custom transport type, do not create an attribute with name URI. This conflicts with a WebSphere Partner Gateway reserved keyword. You will not be able to create and save any destination of that transport type. For example: URI should not be used. Resolving WebSphere Partner Gateway errors BCG210031 and BCG240415 WebSphere Partner Gateway continually attempts to process the same document, issuing the following errors: BCG210031: Unable to Non-Rep document {0} BCG240415: AS Packager Error: {0} The following is an example of the messages that the router.log file contains: 17 Oct 2005 17:55:30,681 ERROR [BPEEngine] [main Thread 1] - Error in nonRepProcess 17 Oct 2005 17:55:30,681 ERROR [BPEEngine] [main Thread 1] - java.io.FileNotFoundException: /opt/wbi/ca/common/data/Inbound/process/917/fa/xxx (A file or directory in the path name does not exist.) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java(Inlined Compiled Code)) at java.io.FileInputStream.(FileInputStream.java(Inlined Compiled Code)) at com.ibm.bcg.util.NonRepudiationDbImpl.copyFile(NonRepudiationDbImpl.java (Compiled Code)) at com.ibm.bcg.util.NonRepudiationDbImpl.store(NonRepudiationDbImpl.java(Compiled Code)) at com.ibm.bcg.server.BPEBean.doNonRepudiation(BPEBean.java(Compiled Code)) at com.ibm.bcg.server.BPEBean.processDocument(BPEBean.java(Compiled Code)) 168 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268

REPROCESSOR_HOME=Document Manager installation root
JAVA_HOME=$REPROCESSOR_HOME/java
LOG_REPROCESSOR_CLASSES=$REPROCESSOR_HOME/classes
2.
Run the utility from the command line:
./reprocessDbLoggingErrors.sh
or
reprocessDBLoggingErrors.bat
Disabling JIT in a WebSphere Application Server when WebSphere
Partner Gateway produces a javacore
About this task
When WebSphere Partner Gateway components (Receiver, Document Manager, or
Console) end abruptly and produce a javacore, it is typically because of a problem
with the Java JIT compiler. If this behavior occurs, disable JIT from the WebSphere
Application Server Admin Console.
To disable JIT from WebSphere Application Server:
1.
Logon to WebSphere Application Server Admin console.
2.
Under Servers, click Servers and select the WebSphere Partner Gateway Server.
3.
On the configuration page, select
Java and Process Management
>
Process
Definition
.
4.
In Additional Properties select
Java Virtual Machine
.
5.
Select the
Disable JIT
check box.
Defining a custom transport type
When defining a custom transport type, do not create an attribute with name URI.
This conflicts with a WebSphere Partner Gateway reserved keyword. You will not
be able to create and save any destination of that transport type.
For example:
<
tns2:AttributeName
>URI</
tns2:AttributeName
>
should not be used.
Resolving WebSphere Partner Gateway errors BCG210031 and
BCG240415
WebSphere Partner Gateway continually attempts to process the same document,
issuing the following errors:
BCG210031: Unable to Non-Rep document {0}
BCG240415: AS Packager Error: {0}
The following is an example of the messages that the
router.log
file contains:
17 Oct 2005 17:55:30,681 ERROR [BPEEngine] [main Thread 1]
- Error in nonRepProcess
17 Oct 2005 17:55:30,681 ERROR [BPEEngine] [main Thread 1]
- java.io.FileNotFoundException:
/opt/wbi/ca/common/data/Inbound/process/917/fa/xxx
(A file or directory in the path name does not exist.)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled Code))
at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled Code))
at com.ibm.bcg.util.NonRepudiationDbImpl.copyFile(NonRepudiationDbImpl.java
(Compiled Code))
at com.ibm.bcg.util.NonRepudiationDbImpl.store(NonRepudiationDbImpl.java(Compiled Code))
at com.ibm.bcg.server.BPEBean.doNonRepudiation(BPEBean.java(Compiled Code))
at com.ibm.bcg.server.BPEBean.processDocument(BPEBean.java(Compiled Code))
168
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide