[jBPM] - process can't saved successully
by Wells guo
Wells guo [https://community.jboss.org/people/wguo] created the discussion
"process can't saved successully"
To view the discussion, visit: https://community.jboss.org/message/831729#831729
--------------------------------------------------------------
Hi ,
When i integrated designer and guvnor in my server XXX.com , i can draw work flow chart but when i exe the save action , it will not save the process normally and display the following errors :
ERROR [org.drools.guvnor.server.contenthandler.drools.BPMN2ProcessHandler] (http-XXX.com/ip:8080-10) Connection refused: java.net.ConnectException: Connection refused
the jbpm.xml in process-designer/profile i have modified :
| | <externalloadurl protocol="https" host="XXXXX.com" |
| | subdomain="drools-guvnor/org.drools.guvnor.Guvnor/oryxeditor" usr="admin" pwd="admin"/> |
| | <localhostory enabled="true" timeout="60000"/> |
So , can any one help me about the issue ?
Note: i had removed the authentication function of the guvnor , so is it related with it ?
Thanks !
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/831729#831729]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
Issue with the maven plugin when using an IP address without reverse name resolution
by Dominique Broeglin
Hello!
I encountered an issue when trying to use the jbos-as-maven-plugin to
deploy on a remote JBoss AS server. I use something akin to :
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>7.4.Final</version>
<configuration>
<hostname>10.1.2.3</hostname>
<port>9999</port>
<username>admin</username>
<password>xxx</password>
<filename>${project.build.finalName}.ear</filename>
<name>backend</name>
<skip>false</skip>
</configuration>
</plugin>
And I get the following error :
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not
execute goal deploy-artifact on null. Reason: I/O Error could not
execute operation '{
"address" => [],
"operation" => "read-attribute",
"name" => "launch-type"
}'
at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:155)
at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 23 more
Caused by: java.lang.IllegalStateException: I/O Error could not
execute operation '{
"address" => [],
"operation" => "read-attribute",
"name" => "launch-type"
}'
at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:241)
at org.jboss.as.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:156)
at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:133)
at org.jboss.as.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:167)
at org.jboss.as.plugin.deployment.DeployArtifact.validate(DeployArtifact.java:75)
at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:133)
... 26 more
Caused by: java.io.IOException: java.lang.IllegalArgumentException:
destination address may not be null
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:234)
... 31 more
Caused by: java.lang.IllegalArgumentException: destination address may
not be null
at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:139)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:114)
at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:124)
at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:111)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:94)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
... 33 more
The error is caused by the fact that the IP address I provide in the
<hostname> configuration entry does not have a reverse DNS name
associated with it. A quick workaround is to add a name for it in my
local hosts file and everything works fine. Also, when using the
jboss-cli everything works fine.
I tracked the hostname parameter in the code and I think that the
issue is in the following line of
org.jboss.as.controller.client.impl.ClientConfigurationImpl:
return new ClientConfigurationImpl(address.getHostName(),
port, handler, null, null, createDefaultExecutor(), true);
The plugin gets an InetAddress which works fine, but when entering
this line we try to get the hostname (which does not exist) and we get
nothing back. This is then used later to construct the URI:
configuration.setUri(new URI("remote://" +
formatPossibleIpv6Address(client.getHost()) + ":" +
client.getPort()));
And finally we get the exception shown above.
I'm not familiar enough with the code to try an provide a patch but I
wanted at least to communicate the issue.
Hope this helps,
Dominique
10 years, 9 months
Re: [jboss-user] [JBoss Web Services] - WS access behind SSO
by Libor Krzyžanek
Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] replied to the discussion
"WS access behind SSO"
To view the discussion, visit: https://community.jboss.org/message/831636#831636
--------------------------------------------------------------
So the situation is an application deployed on JBoss 5.1.0.GA (running on JDK6) needs to make a call to a WebService that is deployed behind an SSO layer. Not so big a deal(I thought). I managed to get the certificates and aliases configured to do the SSL negotiation but then started getting the following:
java.net.HttpRetryException: cannot retry due to redirection, in streaming mode
at sun.net.www.protocol.http.HttpURLConnection.followRedirect(HttpURLConnection.java:2337)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1556)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
at org.jboss.remoting.transport.http.HTTPClientInvoker.getResponseCode(HTTPClientInvoker.java:1238)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:339)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:231)
The problem is that the SSO layer uses a redirect to accomlish authentication which does not lend itself to using URL.openStream()
I know how to code the http handling so that the redirect is followed and the correct stream is obtained what I don't know is how to get JBossWS to use custom code for this.
Thanks in advance,
Chalrie
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/831636#831636]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
Re: [jboss-user] [JBoss Web Services] - Client call to Service behind SSO
by Libor Krzyžanek
Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] replied to the discussion
"Client call to Service behind SSO"
To view the discussion, visit: https://community.jboss.org/message/831646#831646
--------------------------------------------------------------
The situation is an application deployed on JBoss 5.1.0.GA(running JDK6) needs to make a call to a webservice that is deployed behind and SSO layer. I've managed to get the SSL configuration accomlished and the started getting this error:
java.net.HttpRetryException: cannot retry due to redirection, in streaming mode
at sun.net.www.protocol.http.HttpURLConnection.followRedirect(HttpURLConnection.java:2337)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1556)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
at org.jboss.remoting.transport.http.HTTPClientInvoker.getResponseCode(HTTPClientInvoker.java:1238)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:339)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:231)
The problem is the SSO layer uses a redirect which doesn't work with URL.openStreamI().
If I was coding the transport myself coding around the redirect would not be a problem.
What I'm trying to figure out is the best way to tell JBossWS to use some custom code there.
Ideas??
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/831646#831646]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
[IronJacamar] - Possible mem leak in TX synchronizer on afterCompletion() phase
by Andrey Smirnov
Andrey Smirnov [https://community.jboss.org/people/cheezzario] created the discussion
"Possible mem leak in TX synchronizer on afterCompletion() phase"
To view the discussion, visit: https://community.jboss.org/message/831719#831719
--------------------------------------------------------------
Hello.
Let me introduce the problem
App server ( jboss-as-7.1.1.Final ) which is a part of complex distributed app using CORBA for communication fails with OutOfMemoryError
I've investigated the problem and seems like root cause is inability to clean up txSynchs ( and locks ) maps resided in org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer class.
More detailed:
Collections mentioned above should be cleaned up in afterCompletion() method but TX is unavailable at that stage, so Transaction.hashCode() returns -1 which leads to dangled TX associations.
Right now I don't understand why javax.transaction.Transaction is used as a key in this maps? For me it seems like this code wil always fail.
I've attached modified source code of TransactionSynchronizer which I used during investigation and partial app log with records specific to one TX.
Regards, Andrey.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/831719#831719]
Start a new discussion in IronJacamar at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months