Re: [SignServer-develop] RES: RES: RES: RES: RES: Worker's questions and Error WSDL

[Markus K. <ma...@pr...>]

On 2013-01-17 18:23, Marcos Fontana wrote:
> I've done like you said, but the problem persists. If I run the EJBCA
> application server first, the EJBCA works well and SignServer bugs, but if I
> run SignServer first, SignServer works well, EJBCA bugs. There are some
> resources that the first application server is getting before the other.

Do you get any error message in the server.log when the application
servers starts?

It sounds like there still are some ports that are conflicting.

What I usually do is that instead of changing port I use different
interfaces for the JBoss instances ie. instead of binding to 0.0.0.0, ie
bind one to 127.0.0.1 and the other to 127.0.0.2 etc. This can be done
by setting the -Djboss.bind.address in JAVA_OPTS in
JBOSS_HOME/bin/run.conf. Also remember to make sure to change the bind
address in SIGNSERVER_HOME/signserver_build.properties and
EJBCA_HOME/conf/web.properties so that the JBoss server.xml doesn't have
bindings to the wrong interface.

Best regards,
Markus

> 
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...] 
> Enviada em: quinta-feira, 17 de janeiro de 2013 12:04
> Para: Marcos Fontana
> Cc: signserver-develop
> Assunto: Re: [SignServer-develop] RES: RES: RES: RES: Worker's questions and
> Error WSDL
> 
> On 2013-01-17 15:01, Markus Kilås wrote:
>> On 2013-01-16 12:09, Marcos Fontana wrote:
>>> Yes, i edited the jndi.properties.jboss like you told me:
>>>
>>> # JBoss properites
>>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
>>> java.naming.provider.url=127.0.0.1:11099
>>> java.naming.factory.url.pkgs=org.jboss.naming
>>
>> It looks correct, assuming you configured the SignServer JBoss to use 
>> port 11099 for JNDI lookups.
>>
> 
> Also notice that some lookups are performed internally in SignServer so you
> might have to run an "ant clean deploy" after changing this properties so
> SignServer will be re-deployed in JBoss.
> 
> // Markus
> 
>>>
>>> EJBCA and SignServer has the same hostname that I see no problem.
>>>
>>> What I'm trying to archive is, I need the 2 services running at the 
>>> same time, peoples will create their own certificates and then will 
>>> sign/verify some documents. But this is a academic project, is not 
>>> needed different machines to host each service.
>>>
>>> ==========
>>>
>>> When I you will deploy SignServer, before, I must to copy tomcat.jks 
>>> to p12 folder in signserver folder from p12 folder of ejbca. I just 
>>> want it to read directly by EJBCA folder. I think I'm 
>>> misunderstanding, but I'm trying to use ejbca tomcat.jks that is in
> another application server.
>>
>> The web server keystore is often not changed that frequently, say once 
>> every one or two years, so normally manually copying should be okey. 
>> If you still want to automate this, why not just create a symlink in 
>> p12 pointing to tomcat.jks in the EJBCA folder. An other alternative 
>> could be to set the property "httpsserver.keystore" to the path to the 
>> tomcat.jks in the ejbca folder.
>>
>>
>> Best regards,
>> Markus
>>
>>>
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: 
>>> quarta-feira, 16 de janeiro de 2013 07:23
>>> Para: Marcos Fontana
>>> Cc: signserver-develop
>>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions 
>>> and Error WSDL
>>>
>>> On 2013-01-15 18:05, Marcos Fontana wrote:
>>>> Markus, there is some way to change the naming identifier in the 
>>>> signserver installation to avoid this error? If no, there is another 
>>>> way
>>> to do it?
>>>
>>> Can you describe more what you are trying to achieve?
>>>
>>> >From the stacktrace below it looks like either you are using the 
>>>> SignServer
>>> CLI but connecting to EJBCA or that you use EJBCA and connecting to 
>>> SignServer.
>>>
>>> If you are running multiple JBoss instances on different hosts and/or 
>>> ports, are you sure you have changed jndi.properties.jboss and run 
>>> "ant deploy" so jndi.properties contains the right hostname and JNDI 
>>> port for the JBoss running SignServer?
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>>>
>>>> Regards,
>>>>