[Remoting] - Who is responsible for setting the http.proxyHost
by adinn
I'm running into a problem when trying to use a proxy with JBossWS (native 3.0.2 on AS 5.0.0.CR1). I have started my AS with -Dhttp.proxyHost=xxx and -Dhtttp.proxyPort=yyy on the command line. It turns out that the metadata that JBossWS passes to the remoting Client when trying to establish an HTTP connection for a Web Service invocation does not specify an http.proxyHost nor an http.proxyPort.
So, who is responsible for detecting the system properties? I know the remoting code in HTTPClientInvoker used to look at these settings but it definitely does not do so now. Is this a bug introduced into remoting? Or is JBossWS (and, by implication, any other remoting client) now expected to check these system properties and ensure the metadata is appropriately configured?
n.b. the system property settings do seem to be taken into account elsewhere in the AS. For example, if I don't supply them I have problems seeing the jsp index page which provides access to the service. If I do supply them I can see the jsp page, but still cannot access the web service.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168789#4168789
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168789
17 years, 8 months
[JNDI/Naming/Network] - Datasource is null
by badam571
Hi there, I have the following problem, I am trying to connect to database via Jndi but I get datasource is null, here is my codes:
try {
ic = new InitialContext();
ds = (DataSource)ic.lookup("java:/SybaseDS");
conn = ds.getConnection();
}
catch(NamingException ne)
{
logger.debug("Naming Exception thrown: " +ne.getMessage());
}
catch(Exception e){
logger.error("Other connection Exception thrown: " +e.getMessage());
}
return conn;
}
the jndi name on sybase-ds.xml is (I am using Sybase)
<local-tx-datasource>
<jndi-name>SybaseDS</jndi-name>
the database url:
<connection-url>jdbc:sybase:Tds:wi3db1.caci.com:5000/SQ3XX</connection-url>
<driver-class>com.sybase.jdbc2.jdbc.SybDataSource</driver-class>
and the mapping is:
<type-mapping>Sybase</type-mapping>
other config files uses java:/SybaseDS as data-source name
here jbobssjaws.xml:
java:/SybaseDS
<type-mapping>Sybase</type-mapping>
false
here is standardjbosscmp-jdbc.xml:
java:/SybaseDS
-------------------------------------
is there anything I making wrong
Best Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168780#4168780
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168780
17 years, 8 months
[JBoss jBPM] - Re: reopen a process instance ?
by kukeltje
anonymous wrote : And not create a 'big' process where you deal with one dossier until it is finished.
Depends... an simple insurance claim could be dealt with within one process, more complex claims which could take many years (e.g. personal injury) maybe not. And certainly do not look at a morgage as being a process.
anonymous wrote : Would you create tiny processes for any of those tasks ?
You could if you want to take advantage of one tasklist, reminders etc...
anonymous wrote : which might not be very consistent, since in the one case you'll create process variable (eg. dossier id) and in the other you'll have to create task variables for the same data)
Keep task data as minimal as possible... just like processdata. Store all that in your domain model and just reference it
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168769#4168769
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168769
17 years, 8 months
[Security & JAAS/JBoss] - Unable to connect via SSL port
by sagimann
Hi all,
Seems like something as simple as setting up SSL for JBoss 4.2.2 is something I am unalbe to perform :-(
I've created a keystore:
| keytool -genkey -keystore serverkey.jks -storetype jks -storepass changeit -alias tomcat
| What is your first and last name?
| [Unknown]: jboss
| What is the name of your organizational unit?
| [Unknown]: orgunit
| What is the name of your organization?
| [Unknown]: org
| What is the name of your City or Locality?
| [Unknown]: city
| What is the name of your State or Province?
| [Unknown]: state
| What is the two-letter country code for this unit?
| [Unknown]: st
| Is CN=jboss, OU=orgunit, O=org, L=city, ST=state, C=st correc
| [no]: yes
|
| Enter key password for <tomcat>
| (RETURN if same as keystore password): changeit
|
I configured the connector in:
V:\tmp\jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml:
| <Connector port="8181" protocol="HTTP/1.1" SSLEnabled="true"
| maxHttpHeaderSize="8192"
| emptySessionPath="true"
| maxThreads="150" scheme="https" secure="true"
| clientAuth="false" strategy="ms"
| address="${jboss.bind.address}"
| sslProtocol="TLS"
| keystoreFile="${jboss.server.home.dir}/conf/serverkey.jks"
| keystorePass="changeit"
| truststoreFile="${jboss.server.home.dir}/conf/servertrust.jks"
| truststorePass="password"
| />
|
then I simply run jboss using:
run -b 0.0.0.0
and try to access jboss homepage via the browser:
https://myhost:8181
and I immediately get "Internet Explorer cannot display the webpage".
The non-SSL homepage is fine: http://myhost:8080
netstat -aon | findstr LISTEN | findstr <jboss PID> yields everything double, I don't know why:
| TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:1099 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:4446 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:8181 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:18083 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:64330 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:64331 0.0.0.0:0 LISTENING 3156
| TCP 0.0.0.0:64333 0.0.0.0:0 LISTENING 3156
| TCP 192.168.1.4:3873 0.0.0.0:0 LISTENING 3156
| TCP [::]:1098 [::]:0 LISTENING 3156
| TCP [::]:1099 [::]:0 LISTENING 3156
| TCP [::]:4444 [::]:0 LISTENING 3156
| TCP [::]:4445 [::]:0 LISTENING 3156
| TCP [::]:4446 [::]:0 LISTENING 3156
| TCP [::]:8009 [::]:0 LISTENING 3156
| TCP [::]:8080 [::]:0 LISTENING 3156
| TCP [::]:8093 [::]:0 LISTENING 3156
| TCP [::]:8181 [::]:0 LISTENING 3156
| TCP [::]:18083 [::]:0 LISTENING 3156
| TCP [::]:64330 [::]:0 LISTENING 3156
| TCP [::]:64331 [::]:0 LISTENING 3156
| TCP [::]:64333 [::]:0 LISTENING 3156
|
I also have GlassFish v2 installed on the same box, and if I shut down Jboss and start GlassFish (same ssl port), I can reach the GF homepage without any problems. So it's not a Firewall issue.
any ideas why SSL is not working properly and how to diagnose this?
thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168768#4168768
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168768
17 years, 8 months