Re: [Ejbca-develop] EJBCA Hung!

[Tomas G. <to...@pr...>]

Aha, no we haven't tried JBoss 3.2.4 yet. It should be possible to 
rather easily modify the original tomcatxx-jbossyy.xml file. All that is 
needed for EJBCA is SSL requiring client certficate authentication on 
port 8443.

We'll try to add support for it to the next release.

Cheers,
Tomas

Developer wrote:

>I think I figured out the answer to my problem which leads to another
>question.
>
>I'm convinced that my hanging issue is due to an incorrectly configured
>tomcat41-jboss32.xml file.  I'm using JBOSS 3.2.4RC1 which is based on
>tomcat5.X.
>
>Do you have an equivalent tomcat50-jboss324.xml file for tomcat?
>
>I've started looking into it but I'm not familiar enough with Tomcat or
>what is needed for EJBCA.
>
>Thanks,
>
>Chris
>
>
>On Tue, 2004-04-06 at 15:04, Developer wrote:
>  
>
>>I'm running the install.sh script and it appears to have hung.  Below is
>>the last output in the hung state.  What am I doing wrong?
>>
>>Thanks,
>>
>>Chris.
>>
>>Last message from install.sh
>>
>>Initializing CA
>>Generating rootCA keystore:
>>DN: CN=CompanyCA,O=Company LLC,C=US
>>Keysize: 2048
>>Validity (days): 365
>>Policy ID: 2.5.29.32.0
>>Initalizing Temporary Authorization Module.
>>Creating CA...
>>CAId for created CA: -1013392277
>>-Created and published initial CRL.
>>CA initialized
>>
>>
>>Setup of Administration Web Interface have started, this will take a
>>minute to complete ....
>>HANGING HERE!!!
>>
>>
>>Last message in JBOSS log.
>>
>>superadmin, Certificate : No Certificate Involved, Comment : Changed
>>status to STATUS_GENERATED.
>>12:31:14,609 INFO  [Log4jLogDevice] April 6, 2004 12:31:14 PM HST, CAId
>>: -1013392277, RA, EVENT_INFO_CHANGEDENDENTITY, Administrator :
>>BATCHCMDLINE, User :
>>superadmin, Certificate : No Certificate Involved, Comment : New status
>>: 11
>>
>>
>>    
>>