[JBoss JIRA] Created: (JBAS-8343) Nmap scan results in error message on server
by Joshua Wulf (JIRA)
Nmap scan results in error message on server
--------------------------------------------
Key: JBAS-8343
URL: https://jira.jboss.org/browse/JBAS-8343
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.0.0.GA
Reporter: Joshua Wulf
When running nmap against the AS server, the following error occurs at the console:
10:05:59,639 ERROR [ServerThread] WorkerThread#0[127.0.0.1:48016] exception occurred during first invocation
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:937)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:515)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1801)
at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:708)
at org.jboss.remoting.marshal.serializable.SerializableMarshaller.getMarshallingStream(SerializableMarshaller.java:90)
at org.jboss.remoting.marshal.serializable.SerializableMarshaller.getMarshallingStream(SerializableMarshaller.java:72)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createOutputStream(ClientSocketWrapper.java:223)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:181)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:67)
at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)
... 7 more
Nmap opens a connection then drops it. An error on the server seems like an excessive response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBAS-8001) Greater flexibility in picking bind address
by Brian Stansberry (JIRA)
Greater flexibility in picking bind address
-------------------------------------------
Key: JBAS-8001
URL: https://jira.jboss.org/jira/browse/JBAS-8001
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Consider adding a capability to the AS along the lines of what Bela did in JGRP-1204.
An explanatory comment re JGRP-1204 from Bela:
> might be interesting for you if you want to make JGroups bind to a certain *type* of IP address, but don't know the exact address before startup.
>
> For example, in a cloud environment, you don't usually know the IP address assigned to you instance beforehand, unless you use elastic IPs and dyndns.org entries, for example.
>
> Since cloud provider often charge you for outgoing traffic on public IPs, you don't want replication or distribution traffic to go out over public IPs ! You rather want this type of traffic to use internal IP address, for
> which some provider (e.g. GoGrid) don't charge.
>
> This can be done by setting bind_addr or -Djgroups.bind_addr to a keyword rather than a dotted decimal or symbolic IP address:
>
> * GLOBAL: pick a public IP address. You want to avoid this for
> replication traffic
> * SITE_LOCAL: use a private IP address, e.g. 192.168.x.x. This
> avoids charges for bandwith from GoGrid, for example
> * LINK_LOCAL: use a 169.x.x.x, 254.0.0.0 address. I've never used
> this, but this would be for traffic only within 1 box
> * NON_LOOPBACK: use the first address found on an interface (which
> is up), which is not a 127.x.x.x address
>
> For my could mod-cluster demo, I set bind address to SITE_LOCAL. This works for GoGrid, need to see whether this is also true for EC2 and Rackspace
This also has implications for the AS 7 domain model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBAS-8155) Deprecate use of term "partition" (HAPartition, ClusterPartition, etc)
by Paul Ferraro (JIRA)
Deprecate use of term "partition" (HAPartition, ClusterPartition, etc)
----------------------------------------------------------------------
Key: JBAS-8155
URL: https://jira.jboss.org/browse/JBAS-8155
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 6.0.0.M3
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Minor
Fix For: 6.0.0.Final
The term "partition" should be globally replaced by the term "cluster".
This affects public interfaces (the deprecation of which need to be fully backwards compatible), public implementation classes, member variables, system properties, Javadocs, and clustering documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBAS-8716) run.conf.bat options lost if JBoss run as a Windows Service
by Vitaliy Tkachenko (JIRA)
run.conf.bat options lost if JBoss run as a Windows Service
-----------------------------------------------------------
Key: JBAS-8716
URL: https://jira.jboss.org/browse/JBAS-8716
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other, System service
Affects Versions: JBossAS-5.1.0.GA
Environment: Any Windows
Reporter: Vitaliy Tkachenko
If the service is run by jbosssvc.exe then JAVA_OPTS is predefined and set to "-server". So if JBoss is run as a service the command "if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET" in "run.conf.bat" never allows to continue and set all other options.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBAS-7960) snmp-adaptor.sar: Exporting float jmx attributes does not work
by Marc Schoechlin (JIRA)
snmp-adaptor.sar: Exporting float jmx attributes does not work
--------------------------------------------------------------
Key: JBAS-7960
URL: https://jira.jboss.org/jira/browse/JBAS-7960
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-5.1.0.GA
Reporter: Marc Schoechlin
Assignee: Dimitris Andreadis
Exporting SNMP float values does currently not work with snmp-adaptor.sar.
Detailed are described in this discussion: http://community.jboss.org/thread/150912
This bug can be fixed by the attached patch:
Due to the fact that there is not compatible type in org.opennms.protocols.snmp.*
Float is converted to String.
The attached patch is based on:
${code}
$ svn info
Path: .
URL: http://anonsvn.jboss.org/repos/jbossas/trunk
Repository Root: http://anonsvn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 104117
${code}
The patch:
${code}
ndex: varia/src/main/java/org/jboss/jmx/adaptor/snmp/agent/RequestHandlerImpl.java
===================================================================
--- varia/src/main/java/org/jboss/jmx/adaptor/snmp/agent/RequestHandlerImpl.java (revision 104117)
+++ varia/src/main/java/org/jboss/jmx/adaptor/snmp/agent/RequestHandlerImpl.java (working copy)
@@ -483,12 +483,21 @@
{
ssy = (SnmpObjectId)val;
}
- else if (val instanceof SnmpTimeTicks)
+ else if (val instanceof Float)
+ {
+ /*
+ * Due to the fact that there is not compatible type in org.opennms.protocols.snmp.* we convert
+ * Float to String
+ */
+ String in = String.valueOf(val);
+ ssy = new SnmpOctetString(in.getBytes());
+ }
+ else if (val instanceof SnmpTimeTicks)
{
ssy = (SnmpTimeTicks)val;
}
else
- log.info("Unknown type for " + be);
+ log.info("Unknown type for " + be + "(Type was "+val.getClass().getName()+")");
}
catch (Exception e)
{
${code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBAS-8473) Deployment Exception during Start of JBoss AS (4.2.3.GA)
by Upali Aparajita (JIRA)
Deployment Exception during Start of JBoss AS (4.2.3.GA)
--------------------------------------------------------
Key: JBAS-8473
URL: https://jira.jboss.org/browse/JBAS-8473
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Java EE APIs
Affects Versions: JBossAS-4.2.3.GA
Environment: Window-XP
Reporter: Upali Aparajita
Assignee: Shelly McGowan
Dear Experts,
I have been facing problems in deploying my application in Eclipse IDE. I restared the jboss server and encountered with the error as pasted below -
INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
11:16:45,406 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@657088df { url=file:/D:/eclipse-jee-galileo-win32/eclipse/eclipse_plugin/jboss-4.2.3.GA/server/default/deploy/docmanager.war }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/D:/eclipse-jee-galileo-win32/eclipse/eclipse_plugin/jboss-4.2.3.GA/server/default/tmp/deploy/tmp22832docmanager-exp.war/ deployment failed
state: FAILED
watch: file:/D:/eclipse-jee-galileo-win32/eclipse/eclipse_plugin/jboss-4.2.3.GA/server/default/deploy/docmanager.war
altDD: null
lastDeployed: 1285566401250
lastModified: 1285566401218
mbeans:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.web.deployment:war=docmanager.war,id=1701873887
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/D:/eclipse-jee-galileo-win32/eclipse/eclipse_plugin/jboss-4.2.3.GA/server/default/tmp/deploy/tmp22832docmanager-exp.war/ deployment failed
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.web.deployment:war=docmanager.war,id=1701873887
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/D:/eclipse-jee-galileo-win32/eclipse/eclipse_plugin/jboss-4.2.3.GA/server/default/tmp/deploy/tmp22832docmanager-exp.war/ deployment failed
can anyone let me know the reason why deployment gets failed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months